Closed bonnee closed 5 months ago
Yeah, somethings up with chromium 124 in docker. As a hotfix, I rolled back to the previous image version, since the Alpine APK doesn't store its old versions of packages
ARM images are shipping x86-64 binaries now, so they won't start. If someone needs a quick fix, pull docker.io/charlocharlie/epicgames-freegames:54c98a7c5e5d6b04d2be9f336a319be1b24c876d
Sorry about the chaos. Unfortunately I'm AFK for the next few days, so where it's at now is where it's gonna be for a bit.
No problem, thank you for your continuous development of this app and sharing it with us for free.
Found this comment and removed --single-process
, which seemed to fix it. I had used it as it was recommended to prevent zombie processes. Guess it was deprecated or something...
After the image automatic overnight update, I woke up with an hung up server. I had several chromium processes that were consuming 100% CPU and filled both RAM and swap. I traced the leak back to this container and was able to reproduce the issue after a forced reset of the machine.
I believe the container is spawning infinite chromium processes because
chromiumProcesses
appears empty in the logs when the container tries to kill the failed chromium instance, and I see the PIDs number increasing indocker stats
.Screenshots or Logs