This morning I checked in the central bits of the MemoryPurger. This allows
you to start Chrome with "--purge-memory-button", which will add a button to
the Task Manager called "Purge Memory". Pressing this button will attempt
to free as much memory as possible* from the browser and renderer processes.
My hope is that this will be useful in finding cases where we're using too
much memory; I'd like to eventually hook pieces of this to automatic
signals.
Please let me know anything interesting you find with this.
PK
*Currently purged:
Browser process: History backend, "Web data" backend (search keywords etc.),
Proxy resolver JS heaps, Safe Browsing backend, TCMalloc free pages
Renderer process: Spellchecker, WebCore object cache, WebCore font cache,
WebCore cross-origin preflight cache, sqlite database backing stores, JS
heap, TCMalloc free pages.
Let me know if there are major memory consumers I'm missing.
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
