|
|
|
|
|
by krzyk
3285 days ago
|
|
Why?
You can change the number of processes to e.g. 1000 and you will basically get one process per tab until you reach 1000 tabs, and if you do, you will need really a large amount of memory. one process per tab is specifically why I quit using chrome, it wasn't working even for small amount of tabs (100) it ate RAM like crazy. Mozillas approach is better, user can control how many processes are created - users have control. |
|
If there was one thing that caught my attention with Chrome back when it was released (2008?) it was its reliance on OS primitives (processes) as the building blocks for a stable and secure browser. This is essentially the same argument the Varnish folks did when comparing to other proxy solutions like Squid back in the day. I don't understand why Firefox is taking this route.