Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chrome will aggressively throttle background tabs

blog.strml.net

Post reply on HN
Print view View original

351–360 of 403 posts

Re: Chrome will aggressively throttle background tabs

#351

Post by imchillyb »

porker wrote: post #291
visakanv wrote: post #177

Earlier quoted context omitted.

I use one-tab.com; works fantastically for me. Not a huge stretch to say it changed my life.

One-tab doesn't sync or let you backup to another source (e.g. Dropbox). I use it, but taking manual backups is a pain.

> June 2016 Update: We're currently working on new features including an option for multi-PC cloud sync. This has taken quite a few months to put together due to the huge number of extension users that the cloud sync will need to support. Thank you for all of your feature suggestions, please keep the feedback coming. -OneTab

Re: Chrome will aggressively throttle background tabs

#352

Post by hakanito »

webwalker wrote: post #203
altimin wrote: post #176

Hi, this is Alexander. I'm an engineer on Chromium team working on scheduling and on background tab throttling in particular. Firstly, I want to make clear that we are not shipping this in Chrome 56. We have enabled throttling as an experiment in beta channel to measure impact and collect feedback from web devs. We will aim to ship it in Chrome 57, subject to further feedback. In response to concerns voiced we will d…

> In response to concerns voiced we will disable aggressive throttling when active websocket connection is present. Does this extend to SSE?

+1 for SSE!

Re: Chrome will aggressively throttle background tabs

#353

Post by sengork »

rasz_pl wrote: post #338
sengork wrote: post #327

Earlier quoted context omitted.

I agree, the Presto engine was (and still is) super efficient. We may see something similar come out of the Vivaldi project which is headed by folk who led the Opera <= v12 development who know very well what was lost when Opera moved to Chromium based web engine.

No. Vivaldi like new Opera is just a skinning project. They made UI slightly better, added some missing functionality (mostry tabs and gestures), but they do not touch core engine. Case in point fresh Vivaldi on startup makes 4 connections to Google just to say hi, and will keep sending google delicious pieces of data throughout the day, not to mention hardcoded google DNS in case yours is too slow. How about spammin…

I suspect that you know of this already, but here it is anyway: https://otter-browser.org/

Personally I still have Opera 12.18 installed on every computer as it still is the most swiss-army-knife browser out there for countless reasons. Most of the webpages can be made to work properly in it by adjusting the site preferences.

One thing I am yet to see any of the new browsers be capable of is complete popup blocking. Opera 12.x excelled at this and a complete blackout of popups is 100% achieveable.

Re: Chrome will aggressively throttle background tabs

#354

Post by ec109685 »

nothrabannosir wrote: post #239
codazoda wrote: post #230

Earlier quoted context omitted.

I agree. I prefer it throttle everything but ask me if a page is important enough. A news site isn't important enough to ask for this but Slack is.

To be honest neither is slack. They've got push notifications through web service workers. What for would they need aggressive background activity? I'm not saying this to be pedantic, just trying to nip this entitled vendor mentality in the bud. "We're important so give give give without asking." It's a bit what you see with permissions on mobile: the more famous a company is, the more brazen a permission policy they…

I don't want to switch to slack and wait several seconds before messages update. I'd rather the state be updated beforehand asynchronously.

Re: Chrome will aggressively throttle background tabs

#355

Post by ec109685 »

altimin wrote: post #176

Hi, this is Alexander. I'm an engineer on Chromium team working on scheduling and on background tab throttling in particular. Firstly, I want to make clear that we are not shipping this in Chrome 56. We have enabled throttling as an experiment in beta channel to measure impact and collect feedback from web devs. We will aim to ship it in Chrome 57, subject to further feedback. In response to concerns voiced we will d…

The Apple model of asking user for permission when it notices that a background app is reading your location could be a good model to follow. That way, when you notice a frequently battery hogging domain in the background, even if it uses web sockets, etc., you still prompt the user to throttle.

Re: Chrome will aggressively throttle background tabs

#356

Post by ec109685 »

chowyuncat wrote: post #277
tyingq wrote: post #119

Earlier quoted context omitted.

They are making an exception for tabs that are playing audio. You can see the discussion back and forth, here: https://groups.google.com/a/chromium.org/forum/#!topic/blink... I can see where that will end up though. Everyone who's app was broken by this change will start playing zero volume audio, then the exception will be yanked back. With the web poised to be the new platform for applications, there really needs t…

allow_exception = volume < audible_threshold

Super high pitch noise would get through?

Re: Chrome will aggressively throttle background tabs

#357

Post by divanvisagie »

Love how the one commenter already found a workaround:

Olivier TilleJanuary 24, 2017 at 8:28 AM

>That shouldn't be a problem as apparently "tabs with audio are always considered foregrounded". Source: https://groups.google.com/a/chromium.org/forum/#!topic/blink...

UnknownJanuary 24, 2017 at 8:53 AM

>And there's your workaround. Loop a 1 second null audio file for as long as you need to (please don't).

Re: Chrome will aggressively throttle background tabs

#358

Post by fillskills »

altimin wrote: post #176

Hi, this is Alexander. I'm an engineer on Chromium team working on scheduling and on background tab throttling in particular. Firstly, I want to make clear that we are not shipping this in Chrome 56. We have enabled throttling as an experiment in beta channel to measure impact and collect feedback from web devs. We will aim to ship it in Chrome 57, subject to further feedback. In response to concerns voiced we will d…

User should have a way to enforce throttling on all tabs. e.g. I always have my iPhone on low power mode. Its the users choice, not the developers. As much as I hate saying that as a developer.

As an example - I never listen to audio/video in a background tab, but I have to suffer battery loss because of features that I have no plans to use.

Re: Chrome will aggressively throttle background tabs

#359

Post by kakarot »

jklinger410 wrote: post #233
kakarot wrote: post #148

Earlier quoted context omitted.

I use pinned tabs extensively and I prefer that they are throttled even more aggressively than standard open tabs. As long as streaming doesn't break. I have an option set in FF's about:config that disables loading of my pinned tabs on startup, so I regularly keep 200-300 tabs open and only activate the ones I need. Sometimes it takes weeks to clear my tabs because I barely see a performance hit from having so many o…

Unfortunately this doesn't seem to be the way most users are using pinned tabs. Check out the great suspender. The only tabs it does not freeze are the pinned tabs. Extending that functionality to throttling seems natural to me.

It looks cool. Browser memory isn't too much of an issue for me because I run NoScript and uMatrix and thus most of the tabs I have open aren't each running an instance of Google Analytics and stuff like that.

Re: Chrome will aggressively throttle background tabs

#360

Post by gdrulia »

mjburgess wrote: post #187
altimin wrote: post #176

Hi, this is Alexander. I'm an engineer on Chromium team working on scheduling and on background tab throttling in particular. Firstly, I want to make clear that we are not shipping this in Chrome 56. We have enabled throttling as an experiment in beta channel to measure impact and collect feedback from web devs. We will aim to ship it in Chrome 57, subject to further feedback. In response to concerns voiced we will d…

Pinning a tab should disable throttling. Gives user straightforward control over which tabs are important.

Pinned tabs definitely should be excluded from throttling. Pinning tab for me usually means that I want to keep track of something, which usually is my email, chat client, etc. I don't want to be notified about new email on my phone before I get that notification on PC, which is already happening too often. That's just unnecessary hassle.

Though I'm not sure how popular this feature is and I would vote for other ways to turn throttling off, especially for those which prompt user about it.

Post reply on HN