-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[BUG] Navigation failed because page crashed! (Javascript tests) #4655
Comments
Do you also get this message in Chromium with similar to 'Whoops page crashed' which mentions an error code 101 or similar? I have a similar issue on macOs in Chromium |
yeh, the other tab (when I switch to second tab), crashes with the same message. |
@gkushang can you share a script with us that we can run locally to reproduce this? |
@aslushnikov - I just found this Issue via a Google search - I'm not sure if it helps with reproducing/fixing a bug (or if it should be a different Issue altogether), but I get the aforementioned error message when I simply try to load I'm on
|
@rinogo I still cannot reproduce this.. Depending on your environment, this might happen when browser runs out of memory. Do you Would you mind filing a new issue with all the details? I'll close this one since it's not much actionable. |
@aslushnikov Done! #5687 |
Context:
Describe the bug
Error 1
The Page Crash after Navigation. There are many API calls happens to load the heavy page. I use
waitForNavigation=domcontentloaded
and tried others too but it does not load the page. It needs some time to wait rather than crashing.Steps that our test flows go thru,
Login
(lot of navigation happens in the background before page loads)
Click the link -- ERROR (random, 8 out of 10 times)
next steps that also fails (always) when switching to another TAB with same error
Error 2
If I navigate to another URL in the same tab, I get this error
The text was updated successfully, but these errors were encountered: