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. Hope that helps, Charlie
On Wed, May 27, 2009 at 1:53 PM, Mark Larson (Google) <[email protected]>wrote: > See > http://dev.chromium.org/developers/design-documents/multi-process-architecture > and > http://dev.chromium.org/developers/design-documents/process-models > > <http://dev.chromium.org/developers/design-documents/process-models>These > are on http://dev.chromium.org/ by clicking on For Developers and then > Engineering Design Docs. > > Let us know if the documentation doesn't answer your > questions. We want to keep it up to date and useful. > > Thanks, > Mark > > > On Wed, May 27, 2009 at 13:31, Daniel Dreiberg < > [email protected]> wrote: > >> Hi, >> My understanding is chromium has 1 process per tab architecture. >> My question is does chromium has the capability/functionality to: >> 1. if a process/tab runs away (in an infinite loop and taking all cpu) or >> hangs (block waiting for something for some reason, chromium will kill that >> process/tab? >> 2. limit the among of memory that each tab/process can use? >> >> Thank you. >> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
