-
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
chrome process hangs forever #76
Comments
This sounds like the actual Chrome process gets somehow stuck, so that karma can't kill it with a regular signal. Have you checked if Chrome some hangs or reacts to a regular close command? |
@dignifiedquire Here's a high level note https://gist.github.com/beeflamian/07ebb8254e1f92d83296a85610b3fbfe I've also tried to narrow it down by printing stacktrace of chrome. However, I only found chrome is pretty complex that has fingers everywhere. I suspect there is a dead lock among threads :( |
Yeah that looks like Chrome hangs itself for some reason. It's probably related to what is actually run inside your tests. |
I'm seeing the same thing.
The problem appears to be related to Chrome launching a subprocess ( Chrome spawns My brute force solution to this was to remove the following packages:
But it would seem cleaner to be able to launch Chrome in such a way that it does not try to kick start the gnome keyring process. I've no idea how to do that... |
@beeflamian @myitcv Can you repro in the latest Karma? It's possible you ran into this issue which was fixed: karma-runner/karma#2267. |
@voltrevo any reason why you think the two are related? |
It prompts for a password to unlock keychain. But with Chromium (not Chrome) all ok. Also with karma 1.20.
|
Also running into this problem, first of all the docs on karma's 1.0 says it doesn't need anything to open chrome, which is wrong, you still need this plugin, tested on mac. Unfortunately on Ubuntu with the plugin and the CHROME_BIN set, it's having an issue. This was working with the older version of Karma. Here's the stack trace I'm getting:
|
Also, should we open an issue on karma? In it's docs it says chrome comes with it. |
I got the same issue on Windows 10 with:
Screenshot: Relevant Karma Browser config: browsers: ['ChromeNoSandbox'],
customLaunchers: {
ChromeNoSandbox: {
base: 'ChromeHeadless',
flags: ['--no-sandbox'],
},
} When my test suite is empty, then Chrome can be closed by Karma:
|
Hi @bennyn , flags: ['--no-sandbox'] was not worked for me. Still I am getting same Error in Chromeheadless Thanks |
I fixed this on darwin by using the chrome flag --use-mock-keychain |
Any concrete solution to this? This is still happening for me. |
Same problem |
same problem to me |
Same problem. |
same for me |
Setting
Did the trick for for me |
same problem for me too. Any solution appreciated? |
Karma seems have problem disconnecting chrome browser. It happened to me about every 10 tests run. I cannot constantly reproduce this problem
OS: CentOS7
Chrome: Google Chrome 52.0.2743.116
Karma chrome launcher: tried 1.0.1, 0.2.3, 0.1.4, and they all have the problem
Some log:
Finished in 3.517 secs / 2.243 secs
SUMMARY:
✔︎ 9 tests completed
DEBUG [karma]: Run complete, exitting.
DEBUG [launcher]: Disconnecting all browsers
DEBUG [launcher]: Disconnecting all browsers
DEBUG [launcher]: Disconnecting all browsers
...then wait forever
The process tree can be found here https://gist.github.com/beeflamian/336735330443814d442fe77fc8e5f9f4
karma config file can be found here
https://gist.github.com/beeflamian/180dc8565e39509c11ee61f6cf844f38
Does anyone have any suggestions? Thanks in advance!
The text was updated successfully, but these errors were encountered: