Skip to content
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

Closed
gkushang opened this issue Dec 9, 2020 · 6 comments
Closed

[BUG] Navigation failed because page crashed! (Javascript tests) #4655

gkushang opened this issue Dec 9, 2020 · 6 comments
Assignees

Comments

@gkushang
Copy link

gkushang commented Dec 9, 2020

Context:

  • Playwright Version: playwright@1.6.2
  • Operating System: Mac
  • Node.js version: v12.19.0
  • Browser: Chromium

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

     page.reload: Navigation failed because page crashed!
=========================== logs ===========================
waiting for navigation until "domcontentloaded"
============================================================
Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs.

      at Connection.sendMessageToServer (node_modules/playwright/lib/client/connection.js:69:15)
      at Proxy.<anonymous> (node_modules/playwright/lib/client/channelOwner.js:54:53)
  pw:api => page.reload started +1s
  pw:api waiting for navigation until "domcontentloaded" +1ms
  pw:api <= page.reload failed +0ms
  pw:api   "domcontentloaded" event fired +8ms
  pw:api   "load" event fired +0ms

Error 2

If I navigate to another URL in the same tab, I get this error

    [1] <teardown> Error | Error: frame.$: Execution context …
Error: frame.$: Execution context was destroyed, most likely because of a navigation.
@gkushang gkushang changed the title [BUG] Navigation failed because page crashed! [BUG] Navigation failed because page crashed! (Javascript tests) Dec 9, 2020
@weyert
Copy link

weyert commented Dec 12, 2020

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

@gkushang
Copy link
Author

yeh, the other tab (when I switch to second tab), crashes with the same message.

@aslushnikov
Copy link
Collaborator

@gkushang can you share a script with us that we can run locally to reproduce this?

@rinogo
Copy link

rinogo commented Dec 31, 2020

@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 https://www.californiaorganics.com/. Actually, it looks like it crashes "randomly" at different times - sometimes while loading, other times once loading is complete and my script's actions are underway.

I'm on 1.8.0-next (3eef2548e4d55db5970a81582bc0276d814c42da), macOS 10.15.7, and Node v14.15.1.

page.goto: Navigation failed because page crashed!
=========================== logs ===========================
navigating to \"https://www.californiaorganics.com/\", waiting until \"load\"
============================================================
Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs.

@aslushnikov
Copy link
Collaborator

@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.

@rinogo
Copy link

rinogo commented Mar 2, 2021

@aslushnikov Done! #5687

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants