The answer is very simple.
I use Chrome to start the karma server. When you first start the karma server, the Chrome instance starts as a maximized window. So naturally, you minimize this so that you can verify that your tests are running.
The problem is that Chrome stores any minimized or secondary tabs (switchable tabs) of CPU cycles.
Therefore, if you minimize the browser instance on which the karma server is running, or simply switch to another tab, then the karma server is very hungry from the processor, and the tests take a lot of time.
The solution is to keep the karma tab active. The browser window can be hidden behind other windows, but the karma tab should be the selected tab, and the browser should not be minimized.
Following these simple rules, you will always work at full speed.
biofractal Oct 30 '13 at 13:38 on 2013-10-30 13:38
source share