Rogério Vicente

@hansl the aggressive throttling is only enabled by default on Chrome 57. The versions in question are 54 and 55. Still, I'm pretty sure this is not directly related with...

@javigd the only difference between your custom launcher and the default one is that it has the `--no-sandbox` flag and doesn't have the `--disable-gpu` flag. So I would say that...

@hanct that's not supposed to happen. Are you passing the same `--data-dir` as your personal chrome to the karma chrome?

@BenRacicot that's actually the opposite of what @hanct was mentioning. So it's the expected behavior. You shouldn't use your personal chrome instance because the results may be tainted by installed...

@alancnet thanks for submitting this PR and sorry for the delay responding. It's been a while since this PR was created. Can you confirm the issue still occurs?

@squarebracket could you please sign the CLA first?

@beck thanks for the suggestion. Can you do a PR?

Just a heads up, on OSX, headless chrome doesn't behave completely like a background app. If you have a chrome already running, its window will be focused when you start...

@captainjackrana exactly. That is a known problem. I'm not aware of any flag that changes that behaviour. But it seems to me that it is OSX causing it.

Thanks for reporting @mramato I’ll have a look at it as soon as possible.