Live data from Hacker News

Chrome will aggressively throttle background tabs

blog.strml.net

91–100 of 403 posts

Re: Chrome will aggressively throttle background tabs

#91
post #20

I like the change as a general idea but there obviously needs to be a manual override. Like, I don't want websites to access my camera without permission but obviously I want to allow some websites to do that. A similar permission could be used here and is perfectly backwards compatible: 1. a tab exceeds its quota and throttling kicks in; 2. you visit the tab to check why it stopped working; 3. you get a permission p…

Pinned tabs would be an easy solution for this. "Don't throttle pinned tabs"

A common use-case is tabs that are streaming music. I'm not sure if most users are even aware of pinned tabs.

Re: Chrome will aggressively throttle background tabs

#92
post #20

I like the change as a general idea but there obviously needs to be a manual override. Like, I don't want websites to access my camera without permission but obviously I want to allow some websites to do that. A similar permission could be used here and is perfectly backwards compatible: 1. a tab exceeds its quota and throttling kicks in; 2. you visit the tab to check why it stopped working; 3. you get a permission p…

Pinned tabs would be an easy solution for this. "Don't throttle pinned tabs"

While this is elegant, its still dangerous. There are online payments that could check whether your booking is complete in the background by periodically firing ajax calls, bulk updates or uploads, etc.

Re: Chrome will aggressively throttle background tabs

#93
post #84

This sounds a lot like the problem Android had with background tasks. Starting in KitKat, a batching mechanism was introduced, so that apps which declared that they wanted CPU or screen resources in the future didn't all have separate timers running, but instead became members of a class that wanted similar things. One of the most effective features of Greenify, a battery-saving app, is to force all apps (or all apps…

Yep, and Android 6.0 Doze even expanded this mechanism to be more aggressive which proved to provide huge battery savings.

Re: Chrome will aggressively throttle background tabs

#94
post #40

So you get to use 1% CPU, effectively. The timer test seems strange, why was your "simple setInterval" using so much more than 1% CPU?

No, you don't get to use 1% CPU. That would still work. The problem is that you get to use 100% of CPU but only 1% of the time.

Explain how that is different?

Re: Chrome will aggressively throttle background tabs

#95
post #7

Pretty annoying if you want a game to continue running in the background :/

Just what I was thinking. RIP Cookie Clicker.

Wouldn't Cookie Clicker be doing updates based on time deltas? There's no guarantees a timer will fire after the desired time even without this update. Or am I missing a feature that requires it to be able to continually process in the background?

Re: Chrome will aggressively throttle background tabs

#97

Earlier quoted context omitted.

If it doesn't, then why does it grind to a halt eventually on both Mac and Windows? Firefox suffers from the same nonsense as well. In fact, Safari seems to be the ONLY thing I can keep open for more than a day without a process restart.

You're doing something wrong. I use Chrome on Windows as my main now and I usually have more than 100 tabs open. I just switched a few months ago from Firefox on Linux, also usually with 100 tabs or more open. Both are very stable. Chrome is worse with handling tons of tabs, but I certainly don't have daily crashes. People who have extremely unstable/inconsistent experiences with these platforms usually have a rogue…

For every person that has my symptoms, there is someone to counter it. I'm not going to get into an argument about how I'm using my browser incorrectly. Every computer / browser combo I've ever used exhibits the same thing, and I'm pretty religious with keeping things trim and clean.

Re: Chrome will aggressively throttle background tabs

#99
I would like to see Chrome utilize what I think is the right solution for loading background tabs; I would like it to let you (when you want to) rather than OPEN a background tab, only ENQUEUE a background tab -- opening it only when that tab becomes active, meanwhile keeping a barebones tab with that URL in the tabs menu until you actually make it active or it becomes active the way any other tab would, at which point it loads at the same location in the tabs bar that a background tab would have opened.[1]

If this were implemented then finally I could open 120 tabs in a window for a detailed query (and they're not all loaded, there's zero overhead), then after 11 minutes of reading a few of those tabs, closing the ones I've read and having others load in their place if they weren't already loaded, be left with 87 unopened tabs with which I could close, since I've learned everything there is to know about that subject and I don't feel the need to read the rest anymore: I feel I've found the answer.

As it stands I can become an expert in any subject accessible in a day or two, in twenty minutes - unless, as sometimes happens, Chrome gets in my way. I can do it by opening them in background tabs today - but Chrome will just shit itself after a while because it's stupid and feels the need to open a 99th background tab actively just because I may want to read it in a bit. Come on.

Also there needs to be a way (not necessarily the default way) to open private (incognito) windows opened privately "Except for crashes" meaning that it's open until I close it, by clicking the fucking X button, not whenever Chrome decides to barf all over itself (crash) - which usually happens when it's done using all my memory. If you fundamentally disagree that there is a distinction between the user actively exiting and you crashing unexpectedly, then why not change the text to "Pages you view in incognito tabs won’t stick around in your browser’s history, cookie store, or search history after you’ve closed all of your incognito tabs or Chrome crashes unexpectedly".

Doesn't make much sense does it -- So please make the functionality match what you just promised, and keep pages open until I've closed them. Not you.

This stuff would improve people's experiences drastically. It's too bad Chrome's developers don't care about getting Google more clicks, more traffic, letting people open more ads from Google search results, and so forth - by letting people keep more pages and searches open or queued for opening. And that they don't care about their users and give them what they've just promised. Instead, in Incognito windows especially, this stuff just disappears whenever Chrome decides to crash -- which is often, given that it feels like aggressively eating memory for any tab anyone might want to follow.

The web is about links. I hope Chrome will start letting people follow more of them and not lose their trail if they don't want to keep it in their history.

-

[1] Functionality. Right-click a link, click "enqueue", this should be the same as "open in background tab" except the tab is added with the URL in it and it is not loaded until you actually make the tab active. Right-clicking the tab bar should give you the option (in addition to normal options) "Close all enqueued tabs", leaving just ones you've already opened. Example usage: say I'm searching for an article. I can start by doing some obvious Google searches in a few different tabs. I can go through the results and enqueue each one. Then I can go through the first (when it becomes the active tab, it is loaded) and enqueue any links that might lead to what I want. Then I close the now full-fledged tab when I'm done reading and following links, the next tab becomes active (which might have been an enqueued tab in which case it becomes loaded for the first time) and I can keep doing my search. Eventually I've found the page I'm looking for and can close all of the enqueued pages, or perhaps drag the tab into a new window (as you can today) and then close the old window - disappearing all the enqueued pages but also the normal, fully loaded tabs, per the normal behavior closing a window. (An enqueued tab is just a semi-loaded tab, just a URL that never loads until the tab becomes active. If its window or itself is closed in the way you usually close a tab - by right-clicking and clicking "close tab" or by middle-clicking on it, before it was ever the selected tab, then it simply wouldn't have even loaded a single time.)

This is exactly what I do today: except I have to be careful that Chrome doesn't crash while I do it, because it doesn't do it gracefully. I would like to manually specify whether I want the background tan to be actually loaded.

Re: Chrome will aggressively throttle background tabs

#100

It's awesome to see Chrome trying to improve performance for people with many tabs open, which is many of us. I use a LOT of tabs, and the best plugin has been The Great Suspender. Highly recommend it for anyone who wants memory & CPU back and keeps many tabs/windows open at once: https://chrome.google.com/webstore/detail/the-great-suspende...

same here using The great suspender, how does this throttle thing relate to the suspender?
Post reply on HN