-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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] [PW 1.7.0] [WebKit] page.waitForSelector: Protocol error (Runtime.evaluate): The page has been closed. #4764
Comments
@creage can we have a script that we can run locally to reproduce this? It would be hard to understand what's going on without a local repro. |
@aslushnikov I was trying hard to reproduce it manually, but with no success. And by manually I mean running a test on my machine locally. But the issue is constantly reproducible in our CI pipeline, which is Azure DevOps based, and is executed by remote PowerShell script. But still - running same set of tests on same hardware/software environment, ends green running PW So, I took deeper debugging using I have a ~40MB log file, hope it helps. |
Logs show that the page has crashed. We should say "crashed" instead of "closed" in the error message. The only browser log line is about EGL, not very helpful.
@creage If you could share the page url or some test setup where we can try to repro, we could look into why it did crash. Otherwise, the most likely reason is out of memory. @yury-s Any ideas? |
@dgozman I'm not sure I can share the page itself, as it is an enterprise application installed on-prem only. And test setup is really not important, except it being an HTTPS, and manual playing with WebKit executable (WebKit 14.1) gives same results - page refuses to load with some really weird behavior, like scripts are stopping loading in half of the way, style are not rendered, etc. I was monitoring the system, and I never saw any memory issues - it was around 70-80%. But CPU was 100% most of the time. And machine specs are quite normal - they work fine with WebKit 14.0: |
Looks like we need more details to address this one... Closing in hopes that another issue with a repro is filed |
Hello, I can repro similar bugs using the
(I removed two lines of the log to protect our privacy) I'm not using playwright directly. Instead, we use
System:
|
Hello! Our team have the same issue. Local test pass. Remote test (on the https://aerokube.com/moon/) fail because can't wait when page loaded. Tests was start for the same page: https://dasreda.ru/ Context: Code Snippet LOGs |
Context:
Code Snippet
Simple launching a browser and navigating to a page using proxy (both for browser, and for context).
Describe the bug
Test passes on Chrome and Firefox, but fails on WebKit, with error
Test passes fine on PlayWright v1.6.2, in all browsers.
P.S.
Here is
DEBUG=pw:api
output (test retries itself 3 times before it fails):The text was updated successfully, but these errors were encountered: