On Wed, May 27, 2009 at 5:15 PM, Charles Reis <cr...@chromium.org> wrote:
> Those documents are certainly the best place to go to understand the process
> architecture (since it's not strictly process-per-tab, but that is an easy
> way to think about it).
> I think the answers to your specific questions are (1) yes, Chromium will
> prompt you if a rendering engine process becomes unresponsive to give you a
> chance to kill it, and (2) I don't think there's any UI in Chromium for
> placing a memory quota on a rendering engine process.
The exception is that there is a global cap on the memory cache for
web pages and images. This quota is distributed to the renderers so we
don't waste too much space with large caches in each one.
Brett
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
