High memory usage - Accumulates excessive RAM over time and cannot be fully stopped from the UI

Investigated RAM usage inside the Agent Zero Docker container (7.5 GB in use).

Built-in browser accumulates excessive RAM over time and cannot be fully stopped from the UI

My own words

Agent-zero was using 2.5x the amount of memory it usually does(at over 7GB) yesterday.. When i tried to fix it, it wasnt able to without disabling the browser plugin alltogether..

It seems chromium keeps processes running.. Not sure if it is when the agent freezes(i have had a lot of API hickups lately, because of problems at the providers end) But my Agent wasnt able to kill the processes, which is what made it a real problem.. (By the way, today after "fixing" this issue, the plugin hub only shows 7 plugins. ## Ive made another issue report about that, in case it might matter)

Problem

RAM usage of our Agent Zero Docker container grew steadily over ~5 days and stayed high. The built-in browser (Playwright/Chromium) was responsible.

Observed

State	Container RAM	Browser processes
Affected (after ~5 days)	~5.5 GB	~30 processes, ~3.9 GB summed RSS
Normal (expected)	~2.5 GB	0 (browser idle)

One renderer process had run for 5 days and accumulated 573 CPU-minutes while essentially idle.

What we tried

1. Disabled the browser in settings → the ~30 running processes were unaffected, RAM stayed high.
2. Killed all browser processes (pkill -f 'chrome-linux64/chrome') → RAM dropped immediately, but the browser came back on its own shortly after.

There is no way in the UI to fully stop or clean up the browser.

Result after cleanup

Killing the processes worked as a one-off: container went back to ~2.5 GB and stayed stable. But the buildup will happen again with continued use.

Request

• Automatic cleanup of browser processes when tasks finish (or an idle timeout).
• A "restart browser" / cleanup option in the WebUI, so users don't need shell access to the container.

Environment

• Dockerized Agent Zero, observed Sep 4–9, 2026.