Emulationstation crashed and Cannot allocate memory on pi4
-
Let's try to get a full backtrace. Going back to the instructions I posted earlier in the topic:
- install
gdbwithsudo apt install gdb - exit EmulationStation and start a SSH session to your PI.
- run from the command line (via SSH)
gdb -q /opt/retropie/supplementary/emulationstation/emulationstation # at the gdb prompt (gdb) set logging file /home/pi/es_crash.log (gdb) run- wait for ES to crash
- run from the
gdbprompt:
(gdb) bt full #this should dump the crash log to the file (gdb) q # exitPost the crash file (
/home/pi/es_crash.log) to pastebin.com. - install
-
@mitu said in Emulationstation crashed and Cannot allocate memory on pi4:
I tried your advice but no log gets saved. Below are the commands I used:
pi@retropie:~ $ gdb -q /opt/retropie/supplementary/emulationstation/emulationstation Reading symbols from /opt/retropie/supplementary/emulationstation/emulationstation...(no debugging symbols found)...done. (gdb) set logging file /home/pi/es_crash.log (gdb) (gdb) run Starting program: /opt/retropie/supplementary/emulationstation/emulationstation [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1". [New Thread 0xb4e0c160 (LWP 9985)] [Thread 0xb4e0c160 (LWP 9985) exited] [Inferior 1 (process 9982) exited normally] (gdb) bt full No stack. (gdb) qEdit: just realized that I pressed f4 to get to the terminal and it crashed while exiting so maybe it didnt work because of that? I will try again by just launching games.
-
Just tried again ES crashed on startup:
pi@retropie:~ $ gdb -q /opt/retropie/supplementary/emulationstation/emulationsta tion Reading symbols from /opt/retropie/supplementary/emulationstation/emulationstati on...(no debugging symbols found)...done. (gdb) set logging file /home/pi/es_crash.log (gdb) run Starting program: /opt/retropie/supplementary/emulationstation/emulationstation [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1". [New Thread 0xb4e0c160 (LWP 10011)] Thread 2 "emulationstatio" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb4e0c160 (LWP 10011)] 0x001b4fe4 in nsvg__initPaint(NSVGcachedPaint*, NSVGpaint*, float) [clone .isra. 11] [clone .part.12] () (gdb) bt full #0 0x001b4fe4 in nsvg__initPaint(NSVGcachedPaint*, NSVGpaint*, float) [clone .i sra.11] [clone .part.12] () No symbol table info available. #1 0x001b4ff0 in nsvg__initPaint(NSVGcachedPaint*, NSVGpaint*, float) [clone .i sra.11] [clone .part.12] () No symbol table info available. #2 0x001b4ff0 in nsvg__initPaint(NSVGcachedPaint*, NSVGpaint*, float) [clone .i sra.11] [clone .part.12] () No symbol table info available. #3 0x001b4ff0 in nsvg__initPaint(NSVGcachedPaint*, NSVGpaint*, float) [clone .i sra.11] [clone .part.12] () No symbol table info available. #4 0x001b4ff0 in nsvg__initPaint(NSVGcachedPaint*, NSVGpaint*, float) [clone .i sra.11] [clone .part.12] () No symbol table info available. #5 0x001b4ff0 in nsvg__initPaint(NSVGcachedPaint*, NSVGpaint*, float) [clone .i sra.11] [clone .part.12] () No symbol table info available. #6 0x001b4ff0 in nsvg__initPaint(NSVGcachedPaint*, NSVGpaint*, float) [clone .i sra.11] [clone .part.12] () No symbol table info available. #7 0x001b4ff0 in nsvg__initPaint(NSVGcachedPaint*, NSVGpaint*, float) [clone .i sra.11] [clone .part.12] () --Type <RET> for more, q to quit, c to continue without paging--q Quit (gdb) q A debugging session is active. Inferior 1 [process 10008] will be killed. Quit anyway? (y or n) y pi@retropie:~ $But no log to be found in /home/pi/
-
So third time is a charm, here is the log file:
-
unfortunately it doesn't contain the information of where the crash originated. I think my instructions are not correct and the backtrace is not printed in the logs :/.
-
I appreciate your help on this. Do you have any further advice? Im not sure what to do now considering I just started over and the issue persists.
-
Since I can't reproduce it with my data, can you create an archive with all your gamelists (
$HOME/.emulationstation/gamelists), which should have both the list of games and the artwork - no ROMs. ? Let's see if we can transplant your configuration on my system. -
@mitu you want just the gameslists or do you want the scraped media files too? (no roms)
-
Yes, add the scraped media also, since you said you don't have videos.
-
Ok Ill get started on that, it will take me some time to extricate that info since I now have it stored with my roms. Unfortunately it wont be as easy to copy and paste as before.
-
The following commands should zip all
mediarelated.pngfiles into one zip:cd $HOME/RetroPie/roms find -type f | grep media | egrep png$ | zip all-media.zip -@ -
@mitu Ill give this a shot thanks
-
Before I made someone else do a bunch of work trying to troubleshoot my issue I decided to start with a stock image and make changes one by one to see when the crashing occured. I narrowed it down to the nostalgic-neo theme. After I reverted back to the default nostalgic theme and rebooting I haven't had a crash and it's been almost a week. I removed the nostalgic-neo theme from my pi 3 rebooted and it is also stable again. Not sure exactly why this theme made emulation station unstable for me but I'm glad to have finally figured it out. The odd thing is that originally when I was troubleshooting this issue I switched to the carbon theme and still had crashing but maybe if it was some sort of memory issue/leak then I should have rebooted in between tests.
-
@quicksilver
Yeah probably got to reboot for that. I didn't bother looking at the theme when you ruled it out, I probably wouldn't be able to notice anything anyway. Glad you figured it out. -
Hi all, I found out that the problem occurs when the RPi4 is configured to display 4K. If you change the /boot/config.txt and force 1080p, the problem goes away.
-
@Retropia-rd
Hey so i change the
#hdmi_group=1
#hdmi_mode=16
too
hdmi_group=1
hdmi_mode=16But i still getting this error
-
@quicksilver
Hey quicksilver
im having the same thing.
im stuck with that for a month now...
but before that everything was fine like u said.how did u get it fix ? plz :)
-
@shavecat I'm fairly certain my issue was related to the theme I was using, try switching back to carbon theme, reboot your pi and see if that fixes it.
-
@quicksilver
Thank u i will give a try :)so im still getting this on my runcommand.log and the game just go back to emulationsatin
https://pastebin.com/KYeiA7DE
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.