I've checked

kodi.old.log

Here is what I read

2020-10-19 20:57:47.105 T:1945698320 NOTICE: VideoPlayer::OpenFile: /var/recalboxfs/Videos/movie.avi 2020-10-19 20:57:47.107 T:1584391088 NOTICE: Creating InputStream 2020-10-19 20:57:47.116 T:1584391088 NOTICE: Creating Demuxer 2020-10-19 20:57:47.890 T:1584391088 NOTICE: Opening stream: 0 source: 256 2020-10-19 20:57:47.891 T:1584391088 NOTICE: Creating video codec with codec id: 12 2020-10-19 20:57:47.904 T:1584391088 NOTICE: Creating video thread 2020-10-19 20:57:47.905 T:1681900464 NOTICE: running thread: video_thread 2020-10-19 20:57:47.906 T:1584391088 NOTICE: Opening stream: 1 source: 256 2020-10-19 20:57:47.906 T:1584391088 NOTICE: Finding audio codec for: 86017 2020-10-19 20:57:47.907 T:1584391088 NOTICE: CDVDAudioCodecFFmpeg::Open() Successful opened audio decoder mp3float 2020-10-19 20:57:47.907 T:1584391088 NOTICE: Creating audio thread 2020-10-19 20:57:47.908 T:1552360368 NOTICE: running thread: CVideoPlayerAudio::Process() 2020-10-19 20:57:47.920 T:1552360368 NOTICE: Creating audio stream (codec id: 86017, channels: 2, sample rate: 48000, no pass-through) 2020-10-19 20:57:48.477 T:1681900464 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer

At that moment there is nothing left. Now, I know that the film crashed around 9:05 pm.

If I check:

kodi.log

I get:

2020-10-19 21:05:57.625 T:1945636880 NOTICE: Starting Kodi (18.8 (18.8.0) Git:20201015-nogitfound). Platform: Linux ARM 32-bit

This shows that around 21:05 I restarted kodi. The rest of the file shows no error.

I don't know where to look the error for...

Do some more troubleshooting it seems to occur when more than one game from a system (not including homebrew games) is added as a favorite. I can add any number of homebrew games without issue.

@acris I'll give it a go, thank you.

I confirm library scanning is working back.
Some magic have been done in kernel/filesystem ...
Thanks.

I was able to reproduce the problem (same error messages) on an Asus Eee PC X101CH which has an Intel Atom N2600 CPU that supports EMT64 by default, but Asus disabled this in the BIOS, so I tried the latest x86 build for Recalbox 6 and it crashed just like it was described in this thread.

(Luckily, I was able to find a BIOS mod which re-enabled EMT64 support and after that I was able to boot the x64 version of Recalbox 6 on the very same device.)

@sag508 it's a known issue. Thanks.

I'm new to the forums, I'm not quite sure how to do that... Do you need specific files?

@tekkenism i mean not bloated with roms

Thank you very much, I will change it and try again ☺ and by the way this problem has never occurred me on RetroPie (two months ago I was a RetroPie user) with mgba, I suggest to the devs to check what happends and if it is posible fix it for Recalbox 4.1 I will thank you a lot 😀

I've got it working correctly 🙂

I had the wrong path in recalbox.conf; I was using the one from the instructions instead of the one on the marquee in RetroArch.

Thanks for your time and effort!

Tested it out today and after updating I was still set on fade so the bug seems to be to do with that transition and not the slide transition. I've changed to slide and so far no crashes of any kind. I'm running the recalbox custom theme. The crash seemed to happen only when backing out of a menu, instead of fading, the screen cut to black and I had to restart the system. Definitely not a temperature issue or power issue. Anyway, switching to slide seems to have gotten around the issue. Cheers,   Tim

I got it...   Reason was simply my pi2. It was completly unstable, crashing often, no chance with any overclocking.   I exchanged it. With the same SD Cards the new one runs perfect, no more destroyed file systems. Even with overclocking.   Sometimes if Goldeneye N64 freezes i just pull the power cable and it boots up fine.   So i had only bad luck and got first a pi2 which had bad components. The new one is rock stable.

Hi, this is weird. Can you try on an other tv ? With an other keyboard ?