Repository navigation
Replies: 1 comment 1 reply
|
Should be addressed with the latest, keep us posted! |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
The open-terminal Docker container experienced a catastrophic memory leak, consuming all available host RAM (approximately 25.7 GB). This completely locked up the host operating system, preventing SSH and WebGUI access, until the Linux kernel's OOM (Out of Memory) killer eventually intervened and terminated the container.
Environment:
Host OS: Unraid 7.2.3 (Linux kernel 6.12.54)
Deployment: Docker container
Version:
I don't know the best way to check the version
Steps to Reproduce:
I barely tested it earlier today. I asked it to run "print("Hello, World!")", and it succeeded. However, I had not touched it since then.
Expected Behavior:
The container should maintain a stable memory footprint and not consume unbound host resources.
Logs / Evidence:
Below are the host kernel logs showing open-terminal (PID 3809247) consuming ~25.7GB of RAM (anon-rss:25713700kB) before being terminated by the kernel:
Plaintext
Sorry, I don't know what more I can do to figure out WHY it used up all the memory, I ended up restarting the server.
All reactions