This repository has been archived by the owner on May 8, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 372
pyppeteer.errors.NetworkError: Protocol Error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed. #178
Comments
sorry for the noise, right after submitting the issue, I noticed https://github.com/miyakogi/pyppeteer/pull/160/files when I modify the connection.py - the errors go away I'm closing the issue |
… On Wed, Jan 2, 2019 at 10:53 PM zlei9 ***@***.***> wrote:
@romanchyla <https://github.com/romanchyla> how to modify the
connection.py, thank you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#178 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAZIkq8lf4p2mlqvtEV5caZbfUVfrpUBks5u_X6-gaJpZM4ZXNaY>
.
|
@romanchyla Thanks! It is perfect way to slove my issue! |
I have the same error, why isnt the pull request aproved? |
the same error, this issue did not be solved yet. |
so sad, not be solved yet. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
possibly related to #175
pyppeteer is losing connection to chromium browser (maybe because of something that happens inside chromium?). However, when we run the same logic on node.js, we get no erors.
I have attached a script to replicate the issue (apologies, it's not cleaned up - a discovery code afaik)
Here is the output of the script:
9 out of 10 times, I get the error after 15 urls were loaded. This seems to suggest some sort of a timeout (underlaying websocket?)
I tried running with verbose logs, but can't see anything out of ordinary (around the time the DISCONNECT event happens)
The text was updated successfully, but these errors were encountered: