karma-chrome-launcher icon indicating copy to clipboard operation
karma-chrome-launcher copied to clipboard

Published 20 hours ago • verified publisher icon karma-runner

Tests are running slower on the launched chrome browser

Open tgvrssanthosh opened this issue 2 years ago • 4 comments

Summary

Tests are running slower on the launched chrome browser

Steps to reproduce

  1. git clone https://github.com/pluralsight-projects/SampleKarmaJasmineProject.git
  2. Run yarn && yarn run test
  3. By default, it is configured to launch the Chrome browser. There are only three tests and it takes greater than one second in the newly launched chrome.
  4. Now switch the launcher to Firefox by replacing karma-chrome-launcher to karma-firefox-launcher in package.json. Similarly, in karma.conf.js, replace karma-chrome-launcher in plugins with karma-firefox-launcher and replace browsers from Chrome to Firefox.
  5. Run yarn && yarn run test. It will launch Firefox now and the tests run way faster than chrome.

Description

KarmaJS internally spawns the browser in a child process along with a custom user-data-dir

I observed that on spawned chrome (with a custom user-data-dir), the tests are running very slow as compared to other browsers like Firefox.

I have validated the same by running other test runner such as TestemJS which also spawns the chrome with custom user-data-dir.

In the attached screenshots, you can see that on chrome it is taking around 2 seconds to run the tests where as on Firefox it takes less than 200ms.

I also observed that as more and more tests start running, spawned chrome catches up the speed but falls short (even after catching up) compared to running the tests on non-spawned chrome.

I raised a ticket on the chromium team as well for the same https://bugs.chromium.org/p/chromium/issues/detail?id=1406168

I'm raising this ticket here as well so that others will be aware of this issue.

Screenshots

Screen Shot 2023-01-10 at 2 09 49 PM Screen Shot 2023-01-10 at 2 10 46 PM

tgvrssanthosh avatar Jan 10 '23 08:01 tgvrssanthosh

Quick thought: could this be related to #217 ??

pmvald avatar Apr 20 '23 20:04 pmvald

I was having the same issue when using node 14.20x, with node 16.x this does not happen to me.

"karma": "~6.4.1", "karma-chrome-launcher": "~3.2.0"

lferreira07 avatar Jun 07 '23 14:06 lferreira07

Quick thought: could this be related to #217 ??

I tried with '--disable-ipc-flooding-protection' and seeing the same result of slow running tests.

tgvrssanthosh avatar Jun 11 '23 16:06 tgvrssanthosh

I was having the same issue when using node 14.20x, with node 16.x this does not happen to me.

"karma": "~6.4.1", "karma-chrome-launcher": "~3.2.0"

@lferreira07 I'm also on 16.x version of node and still running into the issue. I believe it has something to do with the chromium browser rather than the node version.

tgvrssanthosh avatar Jun 12 '23 03:06 tgvrssanthosh