-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Launch Chrome with --disable-renderer-backgrounding flag #123
Closed
cexbrayat opened this issue
May 5, 2017
· 0 comments
· May be fixed by satoshinakamoto007/bitcore#1135
Closed
Launch Chrome with --disable-renderer-backgrounding flag #123
cexbrayat opened this issue
May 5, 2017
· 0 comments
· May be fixed by satoshinakamoto007/bitcore#1135
Comments
cexbrayat
added a commit
to cexbrayat/karma-chrome-launcher
that referenced
this issue
May 5, 2017
This was referenced May 5, 2017
cexbrayat
added a commit
to cexbrayat/karma-chrome-launcher
that referenced
this issue
May 5, 2017
vbanos
pushed a commit
to vbanos/brozzler
that referenced
this issue
Feb 13, 2018
``--disable-background-timer-throttling`` and ``--disable-renderer-backgrounding``: karma JS test runner uses these to improve chrome performance karma-runner/karma-chrome-launcher#123 ``--disable-hang-monitor``: Suppresses hang monitor dialogs in renderer processes. This may allow slow unload handlers on a page to prevent the tab from closing, but the Task Manager can be used to terminate the offending process in this case. ``--mute-audio``: obvious. The following are part of google safe browsing features: ``--disable-client-side-phishing-detection`` ``--safebrowsing-disable-auto-update`` ``--safebrowsing-disable-download-protection`` Reference: https://peter.sh/experiments/chromium-command-line-switches/
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On macOS 10.12.4 and Chrome 58.0.3029, it appears that my test suite is slow down if Chrome is in the background. #64 should have fixed it a long ago, but a comment is mentioning the
--disable-renderer-backgrounding
flag, so I gave it a try, and it does fix my issue:Before (Angular CLI project using Karma/Chrome):
First run is fast, the following are really slow.
After, with this
karma.conf.js
using the--disable-renderer-backgrounding
flag:The tests run faster:
This may be related to the Chrome issue https://bugs.chromium.org/p/chromium/issues/detail?id=605498#c1
The text was updated successfully, but these errors were encountered: