5 ms·
The problem with Chrome not having such an option is not just limited to startup time when restoring a session. Having too many open tabs causes the resource co
by Erunno 14y ago
The problem with Chrome not having such an option is not just limited to startup time when restoring a session. Having too many open tabs causes the resource consumption to go through the roof (especially RAM and CPU cycles). I can easily have several hundreds of tabs in Firefox (in combination with tab groups) because I usually use different small subsets of tabs during my sessions so the resource usage is quite manageable.
I've said it times and again: Chrome is optimized for a single use case (i.e. few tab users) at which it excels but tends to break down quickly once you leave its comfort zone, unless you have a fairly powerful system. Maybe the project leader nudge, nudge could divert some resources to make Chrome scale better. ;-)