Restarting Chrome on my MBP; back in a few hours.pic.twitter.com/RrsjQzfmXm
-
-
The good news is that tab-restore has gotten *really good* at dealing with my tab-hoarding ways. The bad news is that I'm now going to spend the next ~hour putting all of these windows back onto the virtual desktops from whence they came.
2 replies 0 retweets 4 likesShow this thread -
Replying to @slightlylate
I still remember the last time I had to use chrome for work on a laptop and tab restore basically locked my machine up for about 3 minutes
2 replies 0 retweets 1 like -
Replying to @antumbral
I've got dozens of windows with 3+ tabs in most of of them and tab restore used to be many-minutes lost, but the new throttling really, really works. So much better.
1 reply 0 retweets 1 like -
Replying to @slightlylate
i wonder if tab hoarding for chrome power users is as bad as FF. apparently a significant number of FF users have hundreds of tabs
1 reply 0 retweets 0 likes -
Replying to @antumbral @slightlylate
Firefox is more hoarder-friendly as tabs don't shrink to 5px width in the tab bar :) Also Firefox on Windows IME used to eat less RAM, hence allow hundreds of tabs without halting the machine; multiprocess Firefox (57) slightly reduced the no. of tabs that can be kept though.
1 reply 0 retweets 1 like
There's a pretty direct tradeoff between security and scalability here. Chrome has always gone for the former. New tab lifecycle APIs should let us freeze/discard aggressively, which will help even more. It's why Chrome for Android and CrOS scale so well.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.