Issue metadata
Sign in to add a comment
|
Switch --process-per-tab ignored
Reported by
ema....@gmail.com,
Aug 31 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Steps to reproduce the problem: 1. set --process-per-tab 2. use middle click to open any kind of tab in the background 3. task managers shows tabs still grouped to the same process What is the expected behavior? Each tab in its own process. What went wrong? Tabs opened are grouped Ex.: a google search will use the same process for the search results tab, smallbusiness.chron.com a link opened from that search results page and productforums.google.com as well from the search results page. Did this work before? N/A Chrome version: 52.0.2743.116 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 22.0 r0
,
Sep 13 2016
Can someone please take a look! The issue affects browsing in that if I open a link from google's search results page, that become unresponsive / freezes until the new link finished loading in its tab. It's REALLY annoying! Are we to browse single-tabbed in this age?
,
Sep 14 2016
It appears to be following the process per site model, instead of Process-per-site-instance. Did they switch this? Middle clicking quite a number of tabs from an individual site ends up making the browser laggy and unresponsive. It's made Chrome unusable to me and I've had to switch to Vivaldi.
,
Oct 16 2016
Bump
,
Nov 1 2016
I can confirm this issue, I'll post a couple of pics... The other tabs were opened from the first one, so it's still using the "Process-per-site-instance" model instead of spawning a new process for every tab.
,
Nov 1 2016
This is not what --process-per-tab is for. The middle click behavior is a separate issue, tracked in issue 23815 . The --process-per-tab switch still groups tabs together in the same process if they might be able to script each other, which is necessary to avoid breaking web pages. See http://www.chromium.org/developers/design-documents/process-models: "The process-per-site-instance and process-per-site models both consider the origin of the content when creating renderer processes. Chromium also supports a simpler model which dedicates one renderer process to each group of script-connected tabs. This model can be selected using the --process-per-tab command-line switch." |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ema....@gmail.com
, Aug 31 2016