3 ms·
That's right -- Chrome uses the same process when there is a JS reference between the windows. (In addition, Chrome will sometimes make windows/tabs share a pr
by dbloom 14y ago
That's right -- Chrome uses the same process when there is a JS reference between the windows.
(In addition, Chrome will sometimes make windows/tabs share a process if there are a lot of tabs open, to save memory. There is a limit to the total number of render processes that Chrome will have.)
- taeric 14y agoCool, thanks. I am, not shockingly, curious how this works, now. Is it just a hinting mechanism, or can the rendering process of a tab/window change on the fly? What happens when you go to a new url in an opened tab? (I mean these more as things I'm now interested in. Maybe I'll get off my virtual butt and check the source. Granted, that source tree is less than casually approachable.)
- dbloom 14y agoUnfortunately, I don't know details that specific (I'm not familiar with the codebase either). Maybe ask on IRC? http://www.chromium.org/contact/-chromium-irc http://www.chromium.org/contact/-chromium-irc