ThePorgs/Exegol-images

[BUG] RAM does not get cleared upon closing a graphical application

Closed this issue · 5 comments

Describe the bug

Bug on MacOS with Orbstack and Windows with Docker Desktop

When I open a graphical application like Firefox or Burp the RAM that is used by Exegol increase but never reduce when I close the application, even if I stop the container. It is cleared only if I reboot Orbstack/Docker Desktop

Exemple :

RAM used with a fresh container :
image

Then Open Firefox :
image

Close Firefox :
image

Finally close the container :
image

Sometimes when I close exegol after a session of 2/3h it use like 10Gb of RAM so it stacks up pretty quickly

Steps To Reproduce

Open firefox or Burp in exegol, look at your RAM in your task manager, then close the application and stop the container and look again.

Exegol Wrapper Version

[*] Exegol is currently in version v4.3.1

Exegol container information

It was a fresh new container of the full version of exegol, just created by "exegol start work"

Exception

No response

Additional context

No response

Anything else?

It's my first ever Issue on github so I'm sorry if I made something wrong. I also didn't know if I had to post this in the Exegol WRAPPER project or here.

If any more information is needed just ask and I will do my best.

I honestly have no idea what could cause this. From what I can read from your post, it happens on both OrbStack (macOS) and Docker Desktop (windows). It also happens on both Firefox and Burp.
I don't think the issue is in Exegol it self neither since we don't do anything particular with the apps or GUI.
@Dramelac @qu35t-code any idea on your end?

Seems like an error on orbstack side. Once the container is stopped there is no more resources consumption.
We should open an issue on orbstack repo with a PoC (without exegol if possible).

Seems like an error on orbstack side. Once the container is stopped there is no more resources consumption. We should open an issue on orbstack repo with a PoC (without exegol if possible).

issue on windows docker desktop as well apparently

FYI, Orbstack has release a beta version with dynamic memory.

The complete changelog : https://docs.orbstack.dev/release-notes#v1-7-0-rc1

Maybe try this version to see if the issue is still here ?

Closing this, hoping the new version effectively fixed it
Please feel free to re-open if needed