undefined | Better HN

0 pointstaeric13y ago0 comments

Hmm... interesting. I was honestly under the impression that all tabs (or windows) were separate processes. Are you saying that if you call window.open with a same domain that a new process is not started? (Sadly, I don't have chrome handy to test this right off.)

0 comments

3 comments · 1 top-level

dbloom13y ago· 2 in thread

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.)

taericOP13y ago

Cool, 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.)

dbloom13y ago

Unfortunately, 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

j / k navigate · click thread line to collapse