Check out the "Caveats" section, I believe it has the infos you want:
Frames are currently rendered in the same process as their parent page. Although cross-site frames do not have script access to their parents and could safely be rendered in a separate process, Chromium does not yet render frames in their own processes. Similar to the first caveat, this means that pages from different sites may be rendered in the same process. This will likely change in future versions of Chromium. And from the "Process-per-site-instance" section: ... or if the pages share a script connection (e.g., if one page opened the other in a new window using Javascript). So in summary: - iframes live in the same renderer process as the parent (regardless of domain). - windows opened via javascript (window.open) live in the same renderer process as the opener [*] [*] See Caveats for an exception (when you clear window.opener) On Tue, Feb 10, 2009 at 12:43 PM, drudru <[email protected]> wrote: > > could someone who has access to that document on the website add to > the > process model description. I would be interested in hearing who > chromium > deals with iframes or other entities. > > http://dev.chromium.org/developers/design-documents/process-models > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
