search

ZaDarkSide / js-test-driver

Automatically exported from code.google.com/p/js-test-driver
0 stars 0 forks source link

JSTD runs very slowly when Chrome slave runs in a "background" tab #440

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?

1. Launch Chrome as a slave for JSTD (I di this using the Eclipse plugin)
2. Pin JSTD tab and make it hidden
3. Execute tests (either from Eclipse or from command line)

What is the expected output? What do you see instead?

Eclipse should run tests at a rate of 20 tests per second, but instead it takes 
several seconds for each test.

Workaround is to make tab a separate window

What version of the product are you using? On what operating system?

JSTD 1.3.5 + JSTD Eclipse Plugin 1.3.4e
OS X 10.8.4 (Mountain Lion) + Chrome 28.0.1500.71 + Eclipse Kepler 20130614-0229

Please provide any additional information below.

I think this is very likely to be a symptom of how much CPU resource Chrome 
allocates to tabs running in the "background", but it impacts JSTD to the 
extend that it is not usable.

Original issue reported on code.google.com by andrew.m...@gmail.com on 31 Jul 2013 at 11:19

GoogleCodeExporter commented 8 years ago 
I can confirm that this is intended behaviour for Chrome: background tabs 
setTimeout run at most every second, compared to every 4ms for foreground tabs. 
See: https://codereview.chromium.org/6577021

Original comment by andrew.m...@gmail.com on 17 Oct 2013 at 9:48