Answer the question
In order to leave comments, you need to log in
Why did Google Chrome stop launching a separate process for each tab?
Hello. The whole point of the question is in the title. I know that many spat on eating RAM, but for machines that have this very memory with plenty, the situation was more than advantageous.
Now I see how n processes are running, each for one extension, plus m processes for all open tabs, and m is much less than the number of these same tabs.
At first I thought that one process is allocated for each "window". At first, such a picture was observed. However, this assumption turned out to be incorrect. Sometimes it happened that windows 3-4 were open, and there were only 2 processes for them.
What's the matter? Why did they decide to abandon the good old memory-eating policy? Is there a way to enable this "working mode" without rolling back to the old version?
I complain that one processor core is simply not able to withstand the simultaneous loading of 10+ video tabs, while the entire processor coped with it.
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question