Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[BUG] 'PlaywrightException: Error: Navigation failed because page crashed!' on Linux
See original GitHub issueOS: Ubuntu 20.04 LTS on WSL, Debian GNU/Linux 10 on WSL after adding required dependencies Playwright Java: 0.180.0, 1.9.0-alpha-0 This issue is not observed on Windows 10.
final Playwright playwright = Playwright.create();
final List<BrowserType> browserTypes = Arrays.asList(
playwright.chromium()
);
for (final BrowserType browserType : browserTypes) {
final Browser browser = browserType.launch();
final BrowserContext context = browser.newContext();
final Page page = context.newPage();
page.navigate("http://playwright.dev");
}
playwright.close();
Error log 1.9.0-alpha-0:
[ERROR] 2021-03-07T08:35:31.695Z pw:api navigating to "http://playwright.dev", waiting until "load"
[ERROR] 2021-03-07T08:35:32.264Z pw:api navigated to "https://playwright.dev/"
[ERROR] 2021-03-07T08:35:32.644Z pw:api "domcontentloaded" event fired
2021-03-07T08:35:30.714Z pw:api => BrowserType.launch started
2021-03-07T08:35:31.545Z pw:api <= BrowserType.launch succeeded
2021-03-07T08:35:31.547Z pw:api => Browser.newContext started
2021-03-07T08:35:31.565Z pw:api <= Browser.newContext succeeded
2021-03-07T08:35:31.566Z pw:api => BrowserContext.newPage started
2021-03-07T08:35:31.690Z pw:api <= BrowserContext.newPage succeeded
2021-03-07T08:35:31.691Z pw:api => Page.navigate started
2021-03-07T08:35:40.108Z pw:api <= Page.navigate failed
[ERROR] com.microsoft.playwright.PlaywrightException:
Error {
message='Navigation failed because page crashed!
=========================== logs ===========================
navigating to "http://playwright.dev", waiting until "load"
============================================================
Note: use DEBUG=pw:api environment variable to capture Playwright logs.
name='Error
stack='Error: Navigation failed because page crashed!
=========================== logs ===========================
navigating to "http://playwright.dev", waiting until "load"
============================================================
Note: use DEBUG=pw:api environment variable to capture Playwright logs.
at /tmp/playwright-java-6854617622148487159/package/lib/server/frames.js:414:64
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 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 >navigation failed because page was closed! - You.com
If I change the uri to example.com, this error does not occur. I need to be able to navigate to the settings URI...
Read more >2010170 – chromium browser crashes upon launch
4606.61 How reproducible: 10/10 times I tried, I ran into the error. Steps to Reproduce: 1.Launch chromium 2.Wait for it to load 3.Try...
Read more >MATLAB Answers - MathWorks
When running MATLAB R2021b on my Linux machine, it sometimes crashes and the following error message appears in the terminal, or will appear...
Read more >playwright提示：Navigation failed because page crashed!
背景今天运行playwright官网的实例，尽然报错了。上周相同的用例还是可以执行的啊提示信息如下： Navigation failed because page crashed!
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 Free
Top 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
‘likely more hassle to maintain browser dependencies up to date on Debian’ – yes, especially for WebKit in my experience. After few attempts I switched to WSL2 Ubuntu. Thanks!
Upgrade from WSL1 to WSL2 seems to be fixing the issue, worked on WSL2 Debian with Chromium and Firefox.