+- CentBrowser Forum (https://www.centbrowser.net/en)
+-- Forum: Product Related (https://www.centbrowser.net/en/forumdisplay.php?fid=1)
+--- Forum: Bugs & Suggestions (https://www.centbrowser.net/en/forumdisplay.php?fid=4)
+--- Thread: Resource leak with the "Browser" task (/showthread.php?tid=8723)
Resource leak with the "Browser" task - tanquang - 01-21-2026
I always use incognito mode, but after updating to v5.2.1168.83, I discovered that the "Browser" task (apparently) wasn't garbage collecting, leading to a very rapid increase in the memory footprint. When the memory footprint exceeded 200,000K+, every time I opened a new tab (both the new tab and the webpage), it would lag for a few seconds, and CPU usage would increase by 100+.
Even after I tried killing all tabs, the memory footprint of the "Browser" task continued to grow (though it slowed down), and the CPU usage remained consistently between 1 and 10+.
I've identified several (possible) causes:
1. Blob storage isn't garbage collected:
When checking chrome://blob-internals/, I found many blobs listed there, some with very large lengths (see attached image below). With the increasing memory footprint of the "Browser" task, more blobs are being created here.
Because it's incognito mode, the "Delete browsing data" feature is completely useless. Even when opening a regular tab and checking chrome://blob-internals/, I see many other blobs there, even though I'm not browsing with a regular tab.
2. Affected by other Chromium-based browsers:
After opening CentBrowser, every time I open other Chromium-based browsers or Chromium Embedded Framework (CEF) Client Applications, the memory footprint of the "Browser" task increases rapidly, by about 30,000K each time if the current "Browser" task's memory footprint is below 200,000K, and gradually decreases if it's already above 200,000K. It seems there's a cross-memory leak here?!
RE: Resource leak with the "Browser" task - S8F8ry - 01-21-2026
1. Are these blob storage occupied by extensions?
2. This may be because the panel only displays the dedicated memory of the process, and when starting other Chromium programs, a portion of the shared memory is allocated to the dedicated memory of the browser process, causing the displayed value to increase.