Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrome 56 Will Aggressively Throttle Background Tabs #77

Open
bauer1j opened this issue Jan 25, 2017 · 2 comments
Open

Chrome 56 Will Aggressively Throttle Background Tabs #77

bauer1j opened this issue Jan 25, 2017 · 2 comments

Comments

@bauer1j
Copy link
Collaborator

bauer1j commented Jan 25, 2017

See:

Chrome 56 Will Aggressively Throttle Background Tabs
http://blog.strml.net/2017/01/chrome-56-now-aggressively-throttles.html

and

Intent to Ship: Expensive Background Timer Throttling
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/XRqy8mIOWps/LvBUbWbxAQAJ

Will that affect this speedtest if the user switches tabs while the test is running (something I often do)?

@jgettys
Copy link
Collaborator

jgettys commented Jan 25, 2017 via email

@bauer1j
Copy link
Collaborator Author

bauer1j commented Jan 25, 2017

As Jim mentions, upon switching tabs, the DSLreports speed test says:

"Test cancelled due to browser tab switch. error:24

For Desktop: Switching browser tabs, or minimising the window, causes the browser to shut down page activity. This means the speed test will be completely inaccurate. Please leave the browser page visible for the short time the test runs. In speedtest preferences if you enable 'Use Web Workers' you may find the test runs in a hidden tab.

For Mobile: Letting the device sleep - or in the case of Android having the screen go dim - shuts down CPU. This means the speed test will be inaccurate. if you touch the screen you can keep it from starving CPU.
"

See also:

https://www.dslreports.com/faq/17964

This doesn't appear to be entirely true though (at least in Chrome). What happens in different browsers or as changes like those proposed in the top issue are rolled out though are something to monitor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants