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] Firefox: Page crashes if page is refreshed or open again

See original GitHub issue

Context:

Playwright Version: 1.20.1
Operating System: docker image based on Ubuntu 20.04
Node.js version: 14
Browser: Firefox 97.0.1 (inside PW 1.20.1)
Extra: CodeceptJS 3.3.0

Describe the bug

My CodeceptJS test opens href links inside main page one by one and checks if page is loaded correctly (no error occurs). Very often a page crashes (but on “random” href link, not on specific one), in Firefox only. It’s O.K. in Chromium

CodeceptJS log (with DEBUG=*browser*)

[2.dev:firefox]     I am on page "https://mysite.cloud/external/courseVariants/list"
2022-03-31T11:58:49.748Z pw:browser [pid=307][err] 
2022-03-31T11:58:49.748Z pw:browser [pid=307][err] ###!!! [Parent][PContentParent] Error: Send(msgname=PHttpChannel::Msg_DeleteSelf) Channel error: cannot send/recv
2022-03-31T11:58:49.748Z pw:browser [pid=307][err] 
2022-03-31T11:58:49.748Z pw:browser [pid=307][err] 
2022-03-31T11:58:49.748Z pw:browser [pid=307][err] ###!!! [Parent][PContentParent] Error: Send(msgname=PHttpChannel::Msg_DeleteSelf) Channel error: cannot send/recv
2022-03-31T11:58:49.748Z pw:browser [pid=307][err] 
ERROR: Page has crashed, closing page!
ERROR: Page has crashed, closing page!
...
ERROR: Page has crashed, closing page!
2022-03-31T11:58:49.968Z pw:browser [pid=307][err] JavaScript error: chrome://juggler/content/content/PageAgent.js, line 13: NS_ERROR_XPC_GS_RETURNED_FAILURE: ServiceManager::GetService returned failure code:
[2.dev:firefox]  › <Error: page.screenshot: Target page, context or browser has been closed>

Issue Analytics

State:
Created a year ago
Reactions:2
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

mxschmittcommented, Apr 11, 2022

Without a repro we unfortunately can’t act on it. Will mark it as p3-collecting-feedback to see if other folks are running into it.

0reactions

pavelfeldmancommented, Oct 20, 2022

Why was this issue closed?

We are prioritizing the bugs based on the upvotes, recency and our ability to act. It looks like this issue only has a handful of upvotes, has not been touched recently and/or we lack sufficient feedback to act on it. We are closing issues like this one to keep our bug database maintainable. Please feel free to open a new issue and link this one to it if you think this is a mistake.