4 ms·

Chrome's policy is pretty much the same; while it can generate a process-per-tab under most conditions, the guarantee it actually makes (in modern versions of C

Chrome's policy is pretty much the same; while it can generate a process-per-tab under most conditions, the guarantee it actually makes (in modern versions of Chrome) is that sites (including different-origin iframes) are isolated into different processes. They use the PSL to determine which sites constitute a different origin, just like Firefox does.

Dylan16807 5y ago
I don't know if "most conditions" is even true. Even when it's only running a handful of processes and I have plenty of ram free I cannot convince it to use more than one process for twitch tabs.
- lxgr 5y ago
  I think there are some restrictions on tab "navigation source". (Something about a fairly obscure JavaScript feature that links tabs opened via click navigation, if I recall correctly.) Does this also happen when you type the Twitch URL in a new tab?
  - Dylan16807 5y ago
    Yes. Or even if I have another tab on youtube or whatever and type in twitch, it will close the youtube process and switch to sharing the existing twitch process.
- staticassertion 5y ago
  > I cannot convince it to use more than one process for twitch tabs. Do you actually want it to? Or are you just experimenting? FWIW There's a flag related to isolation in your chrome://flags that will do per-origin.
  - Dylan16807 5y ago
    The bug might be fixed right now but yes I definitely wanted it, because opening a twitch tab was consistently causing the video in the old tab to hang for a couple seconds. > There's a flag related to isolation in your chrome://flags that will do per-origin. What flag is that? I even tried setting --process-per-site-instance and it had no effect.
    - staticassertion 5y ago
      There's "--process-per-tab" and Strict-Origin-Isolation , dunno if that'll work though