-
Notifications
You must be signed in to change notification settings - Fork 672
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
Running in tests mobile chrome emulator kills networking and system - need help with debugging #2864
Comments
Hi @andrzej-kodify, have you tried to open your site in the browser directly (without TestCafe), enable device emulation in mode in DevTools and perform test actions manually? |
Hi @AndreyBelym
It seems to cause hangs when test i=5 is completed and test i=6 starts.
|
Hi @AndreyBelym, I think I've got some luck in reproducing the issue on public URL.
It seems related to video playing in chrome but possibly also somehow to testcafe triggering this problem (I wasn't able to reproduce it manually browsing). Hope this helps. |
Unfortunately, I cannot reproduce the problem with |
@miherlosev |
I don't know. I will check with macOS. |
I've reproduced the problem on macOS (Node 10.11.0, TestCafe 0.23.0). |
I ran the provided test example on Window and MacOS systems. All works fine on Windows, but Google Chrome begins to hang after 15th test loop on MacOS. |
This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow. |
Are you requesting a feature or reporting a bug?
Bug
What is the current behavior?
I'm running tests in
chrome:emulation:device=iphone 6
. After few tests first my networking diesWhen that happens (and I can reproduce it on every run) dns resolve stops working, basically no network activity works.
If I don't kill testcafe immediately after few seconds everything on my Mac starts to crash, system is not responsive and I have to hard reboot to make it work again.
If I comment out first few tests it hangs as well so it's not a particular test case that causes fail).
I've also noticed that as the tests go it takes longer and longer for the browser to get responses for HTTP requests (until finally it can't get them anymore) - same thing happens on our Jenkins server.
What is the expected behavior?
Obviously continuing tests without issues. I'd appreciate hints about debugging this, I'd be glad to provide as much info as I can.
My suspect would be either testcafe proxy or a bug in Chrome itself.
How would you reproduce the current behavior (if this is a bug)?
It happens only on my internal site that I'm testing (with lot's of images and video playing in background). Unfortunately I cannot share it since it's intranet. I wasn't able to isolate what exactly causes this.
Specify your
The text was updated successfully, but these errors were encountered: