4 ms·
I wouldn't be too quick to blame Chrome. What if each open background tab is running a computation/upload that requires the DOM? What if you're listening to mus
by btown 14y ago
I wouldn't be too quick to blame Chrome. What if each open background tab is running a computation/upload that requires the DOM? What if you're listening to music in the background? Point is, Chrome can't just arbitrarily decide to pause execution and free up memory for background tabs.
Me, I'm a documentation-holic. I need to have all the references for whatever project I'm working on a single click away. Sometimes that will be working with a very specific library, so there's no point in replacing my entire bookmarks bar with all the documentation links for that. I'd normally just leave everything in tabs, and when I run out of memory when I need to launch a memory-heavy app, I'd go to Chrome's Task Manager and kill those tabs. So this is a godsend for me.
- DennisP 14y agoThere are very few cases where I actually want tabs running in the background, and I'd be happy to add those cases to a whitelist in exchange for Chrome not eating my computer. But as long as no browser does that, OP's option looks like a huge timesaver for me.
- joshmlewis 14y agoBut you're a power user, most users wouldn't want the hassle of adding sites to a whitelist.
- Sunlis 14y agoIf something like that was implemented, I would hope that it would be turned off by default and hidden away under the "here be dragons" section of Chrome's settings.
- DennisP 14y agoDepends on the interface. An item in the wrench menu saying "run page in background" would be easy enough for anyone.