Update From Source Fails when Running Detailed Themes - Low Memory

[TMNTturtlguy]

I will be submitting this on github but wanted to see if someone on here has any ideas. @pjft and I have been running some tests and here is what I can share and report:

Running RPI 3B with 2.5power supply with updated retropie 4.2 updated to most recent update on 5/6/2017.

When running a theme, like Comic Book Theme that uses a large amount of memory, updating emulationstation from source fails. I have run tests 6 times and I fail each time at:

81% building CXX objetct es-app/CMakeFiles/emulationstation.dir/src/gamelist.cpp.o

With this error code showing up sometimes, other times it stalls for several hours with no error, just frozen:

[1094.865873] Write-error on swap-device (179:0 :3925616)

Testing: To test this I changed my theme to Carbon. Ran an update from source on Emulationstation and it updated properly. I then changed back to comic book theme, updating failed at 81%. I then tried updating an es update script from @pjft to his ES build. This updated was from the experimental packages and update from source. This also failed at 81%. Changed back to carbon, updated @pjft build, updated properly. Again using carbon, i updated to the main branch es from source, updated properly.

I now switched to comic book theme, i updated form binary. SUCCESS.

Now I switched back to the comic book theme and updated from source. Failed at 81%. This time I exited ES to command line and entered the setup script manually, updated from source, this updated successfully.

Next step, I opened /home/pi/RetroPie-Setup/scriptmodules/supplementary/emulationstation.sh and I modified line 145 to rpSwap on to 750. Again tried to update the main branch of ES from source. Again it failed.

Last step, I modified rpSwap on to 1024 Again I tried to update the main branch of ES from source. This time it successfully updated. I attempted to update the script from @pjft and this was also successful.

[BuZz]

Wait for a reply on the forum before opening a ticket (the issue tracker clearly says to use the forum first - it doesn't mean use the forum then post to the issue tracker). I dont have the time to answer things twice.

[TMNTturtlguy]

@BuZz Sorry, had this discussion buried in another thread and thought we had a solution that might work. My misunderstanding of process. original thread

If you do have a moment, can you explain why you think this is an sd card issue if I can update from source with a simple theme like carbon, but not when using a more complex theme? I would be glad if this is the case, as I would like to rule out the fact that the theme might be causing the issue, but in my testing, i could not do that.

Thanks again for your time and sorry for me errors.

[BuZz]

@TMNTturtlguy I've replied on the ticket. Exit es if building from source. Swap shouldn't fail if being used heavily. Sounds like sd card problems, but could be os. I don't want to add more swap as it would mean large swap file being created when not needed in many cases (with the current calculated swap size code).