Freezing when editing MetaData
-
I keep forgetting about this problem... Yeah, ES just wasn't built with this many systems installed in mind. It can be done though! I'd like to tackle that problem but when I have time to work on ES it is mostly for Gridview. @dominus, I'm just curious.. but could you enabled FPS in UI settings and tell me how much VRAM you are using right as it freezes?
-
@jacobfk20
70.9fps, 14.11ms
VRAM: 189.04mb (texs: 147.09mb, fonts: 41.94mb)I am going to try to do the update here later today too.
-
@herb_fargus , @jacobfk20 Just updated, but still does it. This time even the fonts and images were blocky or not showing up.
Just checked the split and it was set to 256. I put it to 512, and it mentioned something about device specific splits were detected and have been cleared.
I rebooted, and it froze with 73.0fps, 13.70ms, VRAM: 173.16mb (texs: 143.80mb, fonts:29.36mb). I'm going to try GPU split and see if that does anything, but it looks like I'm just gonna have to scrap some systems, or I thought maybe run them only when I have a certain USB in, but linking and putting all the roms on 2 USB drives, and only ever having 1 of them in?!?
-
Upped the Split to 768, but it still froze, so I am guessing it has nothing to do with that?!?
-
@Dominus Try a new power supply and or sd card.
If you read the documentation it will answer 99% of your questions: https://retropie.org.uk/docs/
Also if you want a solution to your problems read this first: https://retropie.org.uk/forum/topic/3/read-this-first
-
@Dominus Even with a 2.1A power supply on my Pi3 I still can't cause this. I am forcing my vram to overflow, currently setting at 285mb and it is running at 45fps in the Edit Metadata menu. As @herb_fargus said, swap the sd and power and see what happens.
-
@Dominus can you better describe what is this "freeze"?
Please, try to answer these questions:- after freezing, are you able to quit emulationstation with F4?
- after freezing, are you able to connect to your pi via SSH?
- if yes, can you run htop (or other process monitoring tool) to check if emulationstation is "eating" your CPU/MEM?
-
@herb_fargus I don't have 2.5a power supply at the moment, so just using a 2.1a. They are hard to find lol. Can I plug it into one of my computer's USB 3.0 slots, and will it be sufficient enough to power it? I will try to swap SD cards later to see if this fixes anything aswell.
@meleu I can't press f4, but I am able to get into SSH. I ran htop, but I have no idea how to read this thing:
-
It looks like you're running ES six times?
-
@jacobfk20 I assume that's not normal? I did not do anything to make it run 6x haha.
-
I've only ever used top, which I am assuming is what htop is, but see if you can kill those extra ES's. you can do that with:
kill [pid]wherepidis the process ID. Hopefully they wont all restart when you run ES again. -
@jacobfk20 said in Freezing when editing MetaData:
It looks like you're running ES six times?
htop shows individual threads as separate processes by default. :-)
-
Ah, ok. Good to know.
-
I noticed that ES isn't very CPU intensive, but there's something being processed. So it's not an actual freezing.
The first time I faced that issue exiting ES with "save metadata on exit" on, I thought ES froze. I never waited those 5 minutes until @herb_fargus answered a topic I started here in the forum and I realized that it actually was processing data and wasn't frozen.
-
I think we have a conclusion here:
ES doesn't freeze when editing metadata. It just takes ages to process metadata changes. :-) -
@meleu I'll try leaving it and seeing if it comes back to life, but as I said before sometimes even just hitting 'select' on a rom will do it, which isn't necessarily the metadata. I'm sure I've left it for 10 mins once and nothing...
-
@Dominus My collection is this big:
game list size:
Atari2600: 1443
FBA: 1
GameBoy Advance: 10
Master System: 545
Mega Drive: 1239
NeoGeo: 7
NES: 2141
PC Engine: 2
SNES: 2271And took 5 minutes to exit emulationstation when "save metadata on exit" was on. OK, I know you are not doing the same task as me, but your collection seems to be a a way bigger than mine and maybe it takes a lot of time to process everything it's trying to process...
-
@meleu @jacobfk20 @herb_fargus Well tried a different SD card, but no luck. I waited over 30 mins when it just locked up. The screen had a fuzzy bar at the bottom?
I could still log into SSH, so it's not like the Pi froze, just ES? Not too sure.
I am going to try a fresh image with the 4.0.2 download.
Here were my systems I was running:
Arcade: 82
Atari 2600: 544
Atari 7800: 68
Lynx: 86
Coleco: 159
GameGear: 280
GameBoy: 154
GameBoy Advance: 34
GameBoy Color: 14
Genesis: 781
LOVE: 2
Sega Master System: 253
MSX: 48
Nintendo64: 5
NES: 798
NeoGeo Pocket: 6
NeoGeo Pocket Color: 43
Kodi: 1
PC: 7
TurboGrafx-16: 104
Ports: 4
PSP: 10
PSX: 86
SCUMMVM: 9
Sega 32x: 34
SegaCD: 13
SNES: 810
Infocom: 3
Vectrex: 38@jacobfk20 You said you couldn't get the same results as me, were you running the same amount of systems too? Hopefully a rebuilt SD card will fix it.
-
Did you confirm your GPU mem settings are applied correctly ?
What is the output offree -h? Perhaps you can post your config.txt ?Might be unrelated to GPU memory of course and some bug in ES you are triggering.
To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first
-
Does it help if you temporarily disable some systems ? (eg by renaming their rom folders) ?
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.