Launch Chrome with --disable-background-timer-throttling flag

[IgorMinar]

Chrome Canary will soon support --disable-background-timer-throttling flag. Karma should use it out of the box.

https://code.google.com/p/chromium/issues/detail?id=485425#c21

[pkozlowski-opensource]

Yay!

[zzo]

published to npm as v0.2.2

[jamestalmage]

Awesome!

[maxkostow]

What about setting --disable-renderer-backgrounding as well? People on the linked issue are claiming --disable-background-timer-throttling isn't enough.

[zzo]

Hm ya maybe - never heard of that one - worth a shot - I'll try to repro
the failure

On Wed, Mar 9, 2016 at 11:07 AM, Max Kostow [email protected]
wrote:

What about setting --disable-renderer-backgrounding
http://peter.sh/experiments/chromium-command-line-switches/#disable-renderer-backgrounding
as well? People on the linked issue are claiming
--disable-background-timer-throttling isn't enough.

—
Reply to this email directly or view it on GitHub
#64 (comment)
.

[zzo]

So I am having problems repro'ing this not working. On Mac OSX Version 49.0.2623.87 (64-bit) just the disable-background-timer-throttling flag works as intended. When the Chrome window is minimized or hidden the tests still run at full speed, not throttled. karma-chrome-launcher 0.2.2.
I will also comment on the chrome issue here: https://bugs.chromium.org/p/chromium/issues/detail?id=485425&can=2&start=0&num=100&q=&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified&groupby=&sort=

[zzo]

ok I can repo this using the angular 1.x repo - bummer :(

[mgol]

@zzo Do you know why did the Chrome issue get restricted? I can no longer see it.

[zzo]

Hm yes looks like it has been restricted to Google. The flag appears to
not work completely correctly on OSX but works on linux it about where
we're at so far.
I think they are going to fix the OSX issue but don't know when.

On Mon, Mar 14, 2016 at 4:21 AM, Michał Gołębiowski <
[email protected]> wrote:

@zzo https://github.com/zzo Do you know why did the Chrome issue get
restricted? I can no longer see it.

—
Reply to this email directly or view it on GitHub
#64 (comment)
.

[mgol]

Thanks for the info. Why was it restricted? It'd be valuable to have a public-facing bug about this issue.

[zzo]

I don't know. I asked if they were going to make another bug for the mac
issue.

On Mon, Mar 14, 2016 at 10:07 AM, Michał Gołębiowski <
[email protected]> wrote:

Thanks for the info. Why was it restricted? It'd be valuable to have a
public-facing bug about this issue.

—
Reply to this email directly or view it on GitHub
#64 (comment)
.

[mgol]

Thx. Please let us know here when you have the answer.

[mgol]

Any updates? Do you know why is the bug hidden?

[zzo]

There have been no updates to the bug and I don't not know why it is now
hidden - I can ask

On Thu, Mar 31, 2016 at 7:12 AM, Michał Gołębiowski <
[email protected]> wrote:

Any updates? Do you know why is the bug hidden?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#64 (comment)

[mgol]

OK, please ask. :)

[mgol]

Any updates, @zzo?

[zzo]

Nope - no updates

On Wed, Apr 20, 2016 at 2:27 AM, Michał Gołębiowski <
[email protected]> wrote:

Any updates, @zzo?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#64 (comment)

[mgol]

But did you ask someone about the issue? Or not yet?

Michał Gołębiowski

[zzo]

I have asked but no response - i will reach out directly and see if I can
get a response.
Mark

On Wed, Apr 20, 2016 at 8:22 AM, Michał Gołębiowski <
[email protected]> wrote:

But did you ask someone about the issue? Or not yet?

Michał Gołębiowski

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#64 (comment)

[zzo]

Ok a new bug was just forked off from the old bug:
https://bugs.chromium.org/p/chromium/issues/detail?id=605498#c1

On Wed, Apr 20, 2016 at 8:36 AM, Mark Ethan Trostler [email protected] wrote:

I have asked but no response - i will reach out directly and see if I can
get a response.
Mark

On Wed, Apr 20, 2016 at 8:22 AM, Michał Gołębiowski <
[email protected]> wrote:

But did you ask someone about the issue? Or not yet?

Michał Gołębiowski

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#64 (comment)