New issue
Advanced search Search tips

Issue 677747 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Aug 21
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Feature



Sign in to add a comment

Improve process separation to true process per tab

Reported by harald.r...@gmail.com, Jan 1 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/55.0.2883.87 Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce the problem:
For large tab populations, Chromium groups tabs into teh same process. This becomes a problm when wanting to killing a certain tab or slowdown caused by a large heap for a group of browser tabs
-
When a second tab is opened using "Open link in new tab" this two tabs share process which leads to 30 or so tabs in a single process. This used to be a huge performance problem, now it is just a process distribution annoyance

What is the expected behavior?
A settings enfrocing true one tab one process
Linux can run 4 million processes or so
-
If the user wants to break whatever open-in-new-tab JavaScript relationship is maintained so that no longer works, please let them break that

What went wrong?
Chromium implemented an efficiency strategy that is not right for Linux

Did this work before? N/A 

Chrome version: 55.0.2883.87  Channel: stable
OS Version: 
Flash Version:
 
And the worse crap is how one rendering process blocks scrolling or interaction with a parent tab. This is today the real problem. Locking up the ui is so not Chromium.
Components: UI>Browser>TabContents
Labels: M-57
Status: Untriaged (was: Unconfirmed)
Since this is a feature issue marking it as untriaged for further triaging.

Status: Archived (was: Untriaged)
Archiving old bugs that haven't been actively assigned in over a year.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Sign in to add a comment