[BUG] Navigation failed because page crashed! (Javascript tests)
See original GitHub issueContext:
- 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.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Navigation failed because page crashed! JavaScript Playwright
The "Navigation failed because page crashed" error can also be produced if the system Playwright is running on runs out of available RAM....
Read more >page.goto: navigation failed because page crashed - You.com
Describe the bug I get the aforementioned error message ( page.goto: Navigation failed because page crashed! ) when I simply try to load ......
Read more >Error Messages | Cypress Documentation
This message means that Cypress was unable to find tests in the specified file. You'll likely get this message if you have an...
Read more >Javascript – UnhandledPromiseRejectionWarning: Error: Page ...
So I used a while loop so my test will run in a constant loop until my back-end will crash. ... So indeed...
Read more >Puppeteer documentation - DevDocs
Puppeteer can be used for testing Chrome Extensions. ... <Error>. Emitted when the page crashes. NOTE error event has a special meaning in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@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.@aslushnikov Done! https://github.com/microsoft/playwright/issues/5687