RetroPie randomly freezing/crashing while browsing through game lists.

pjft

Thanks. What EmulationStation version are you in, though? Press start and see.

Are you comfortable with ssh?

Thanks.

beastmode

@tmntturtlguy marquee files range in size from 3 KB to 137 KB, images files from 185 KB to 790 KB, and video viles from 826 KB to 8 KB.

beastmode

@pjft I'm pretty comfortable with SSH. I know my way around, more or less. EmulationStation - v2.4.1rp, built Aug 3 2017 - 17:01:17

TMNTturtlguy

@beastmode the marquee sizes look good, the image sizes in the 700kb might cause some issues in large lists or if using a theme that loads images and videos. I keep my images in the 200kb or lower. I use a png compression program so I don't lose to much quality, but the images are far from HD. I also assume some of your videos are 8mb (your post says 8kb) i don't know a ton about video sizes but I know reduced mine to 320x240 and my file sizes are much smaller.

I hope @pjft has some suggestions, but I would make a copy of all your scraped files and the run a batch convert of your videos using handbreak and a batch reduction in png using a program called riot.

beastmode

@tmntturtlguy Great advice, dude. I'll give that a try right now.

beastmode

@tmntturtlguy Would you say 2 mb to 4 mb for video files is okay?

TMNTturtlguy

@beastmode yeah, that sounds a lot better to me. The smaller the better as long as you are ok with the quality

beastmode

@tmntturtlguy The quality looks just fine to me at 320x240. The images I don't care so much about since the videos are front and center in my setup with your theme =). I'll test for a few and let you know if your suggestion solved my problem.

pjft

Ok all - and adding @BigMan1982 here as he reported the same.

Thanks for bringing this up. If you're keen and open to helping us get to the bottom of this, I'm willing to try my best to figure out what may be happening here.

There are two or three things that I'd ideally want to get to. Bear in mind, though, that consistently getting your Pi to a state where it freezes and you have to pull the plug is not ideal, as you may end up corrupting your SD card, so I'd strongly recommend making a backup of your system and ROMs - regardless of whether you'll be helping test this or not.

Now that I got that out of the way, these are the things I'd be keen on narrowing down:

Exact (or semi-reliable) steps to make it get to that state;
Features that may be related to the behavior;
Version where that might have been introduced - as a proxy to what changes might have brought that up.

Now, for 1, it seems some of you - at least you, @beastmode - seem to have an "easier" time making it happen more frequently.

Would it be possible to ask you to SSH into your Pi, and then run "top", and while it's running attempt to get the Pi into that freezing state? I'd be keen on learning what exactly is happening in the background - if any process starts using up all the memory, if there are any ghost processes dangling, etc. I fact, if you'd want to do it with "htop" instead (you can install it via sudo apt-get install htop) it tends to provide some more details.

Thanks. Also, given that you will have a session connected to the Pi, you may be able to force it to shutdown properly (fingers crossed).

For 2., after this test, I'd probably suggest testing replicating the same behavior in two distinct scenarios: the first, disabling OMX Player (go to Start Menu > Other Settings > Turn "Use OMX Player" to "OFF"). If you don't have OMX Player turned on, then ignore this.

After this - whether you managed to replicate it or not - turn OMX Player back on, and then in the UI settings set it to only display the "Detailed" gamelist. See if you can get it to the same state. This is a very random bug, so don't give up immediately as we may end up disregarding features that may be related, just by pure coincidence of not being able to replicate it.

Once again, always with SSH and htoprunning.

For 3. we'll get to that after we have a bit more data here, if possible. But it'll likely involve me providing older builds to try to track it down further, or asking you to compile some builds on your own if you are comfortable with that. Likely I'll also try to provide a debug build with a lot of logging so that we can hopefully get more data there.

It'd also be helpful from both of you, @beastmode and @BigMan1982 to get a status on:

VRAM setting
ES version
Controller you're using (in particular, bluetooth or wired)
OMX Player or not

Thank you all in advance. I know this will take some of your precious free time, so I am mindful of that. I appreciate any help you can provide here, so that hopefully we can fix this (as long as it can be fixed) for everyone.

I'll also try to chase this down, but I haven't been able to replicate it since yesterday so I'm hoping one of you has a bit more luck with it.

Have a great Sunday, thank you!

beastmode

@pjft I'm only experiencing this problem at the game list menu, never in game or at the system selection screen. Slowly browsing a large game list menu for any system, from top to bottom, pausing for a second or two on each game selection while the scraped video file plays is when my system crashes at random.

OMX Player: enabled
Theme: Comic Book Theme created by @tmntturtlguy
Device Temperature: CPU: 47°C/116°F GPU: 47°C/116°F
VRAM: currently set to 80mb. crashing continued with 100 as well.
ES Version: EmulationStation - v2.4.1rp, built Aug 3 2017 - 17:01:17
Controller: usb connected PS4 controller | usb connected XBOX 360 controller
HTOP: installed. memory usage steadily in the 155mb range while browsing game lists.
Image Artwork: images and marquee .png files, enabled and displaying properly. file size varies from 3kb to 750kb.
Video Artwork: 320x240 .mp4 files, enabled and displaying properly. file size varies from 813kb to 4.5mb.
Overclock: 1.4 ghz. gpu_mem=400, arm_freq=1400, over_voltage=6, sdram_freq=500, core_freq=500, gpu_freq=400, gpu_mem_256=128, gpu_mem_512=256, gpu_mem_1024=256

Steps taken after experiencing the problem, but didn't correct it:

lowering the overclock to 1.35 ghz and 1.3 ghz.
reducing video and image file sizes
updated RetroPie setup and all core packages
changed theme to carbon

TMNTturtlguy

@beastmode - when you start up, do you see a White or Black ES background before it loads to the system select screen?

@pjft - What version did you implement all of the final updates to ES to make it run better? I am wondering if that is the issue?

@beastmode there was an update a while back that @pjft made a ton of updates to how ES uses memory and loads textures. This allowed not only the ComicBook theme to run better, but also made it possible for so many of the new cool themes we are seeing today. I am wondering if you are still on an a version of ES prior to those updates? Can you try to run the carbon theme and see if the problems still exist? You may have already tried this, so i apologize for asking. I assume the file size reduction has not helped? I still see you listing your images as high as 750kb.

Thanks

beastmode

@tmntturtlguy the ES background is black. Which version of ES are you using, and how would I go about checking the exact version I have installed? I checked my es_log.txt file which lists the version as: EmulationStation - v2.4.1rp, built Aug 3 2017 - 17:01:17. I also updated all core and main packages including ES through the retropie setup menu. The problem persists with images reduced and nonreduced.

pjft

This is a recent enough version, it'll have all the fixes.

@beastmode if you can replicate it fairly consistently, send over what htop reports on (picture even or copy and paste the text) from when it crashes, after a minute or so.

Also, try with OMX player off and see if it helps.

I spent three better part of an hour today don't what you described on a long gamelist without success on my end :/ But I know it can happen, so I'm hoping you can shed some more details from when it crashes on your end.

Thanks for chasing this with us!

beastmode

@pjft I'll try with OMX player off. My system crashed earlier while htop was open but it didn't record anything at all at that exact moment or there after. It came to a complete halt and I was disconnected from the SSH connection, unable to reconnect at all. Had to pull the plug. The crashes don't seem to be as frequent today as they were the past few days.

pjft

@beastmode Oh. That's unfortunate that htop and the ssh session also died :S

I had hopes that that wouldn't be the case.

I suppose if we won't be able to make it with htop or top, we'll try to fly blind then and just adjust things on ES.

If you could try out the steps I mentioned in 2) including disabling OMX, as you just mentioned, but also forcing it to just show just the detailed view (and if it still crashes, I suppose just the basic view...) to see if we can narrow it down.

Do you have a backup so far, though? These crashes can render your card corrupt - and in fact, I wouldn't be shocked if that wouldn't be what's driving this, in a kind o vicious cycle. Maybe the first time it was a coincidence, but now the more we pull the plug the worse we we do. :S

Thanks!

beastmode

@pjft I have everything backed up =). I thought maybe a corrupt SD card might have been the problem, so I formatted it and started fresh but the problem was still there. I'll test omx and detailed view shortly.

beastmode

@pjft @tmntturtlguy I turned OMX player off, while leaving the Comic Book Theme in Gamelist View Style: Automatic. Crashed after 30 minutes of bouncing around the gamelist. Did the same in Gamelist View Style: Detailed, and have not experienced a single crash in the same time period.

pjft

@beastmode thanks.

So, summarizing: you managed to experience freezes on videos with both players, did I get that right?

If so, that's one less factor to worry about.

If you can keep up the detailed view for a while, let me know how it goes.

It might certainly be related to the video views or playback. Anything that can help narrow this down will be helpful.

No urgency, though :)

Thank you!

beastmode

@pjft That's correct. I'll continue to test all through the evening and report back to you in a few hours. Thank you as well =)

pjft

@beastmode thanks. As I said, no urgency - make sure to have fun with it and play for a while as well :)

If in a few days you haven't experienced any further crashes, I'll put together a build with logging on the video playing but, hoping it will shed some more light.

Thanks! Have a good evening.