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] Connection not closed correctly in v10.1.0 #7407
Comments
our project caused same error which version up from 10.0.0 to 10.1.0. |
@DRoet Do you have any updates on this? I get the same error on |
Nope, best to stay on 10.0.0 for now, there is a PR up trying to fix the issue #7414 but there isn't much traction yet. |
I'm probably running into this issue with one of my project's pipelines, but only on Node 14 and 16 on Windows. |
Unfortunately, I can not reproduce this problem on my machine. Could you maybe share a reproduction? |
I used The error occurrs when I tried downgrading both the puppeteer package as well as the nodejs, but the error kept happening.
Lambda code:
|
Getting this after upgrading from node 14 to node 16. Doesn't happen all the time, but often enough... Extra annoying that there is some unhandled rejection somewhere, so our server just crashes rather than returning at least a 500 error |
This should have been fixed in #7728. |
Steps to reproduce
Tell us about your environment:
What steps will reproduce the problem?
When updating from 10.0.0 -> 10.1.0 I suddenly get an error when connecting to a remote chrome instance using
browser.connect()
. The remote chrome instance I am using is a simplebrowserless/chrome
docker image running on a dedicated portPlease include code that reproduces the issue.
What is the expected result?
Connection closes correctly, no error is being shown. This works fine in v10.0.0
What happens instead?
following error is being thrown:
The text was updated successfully, but these errors were encountered: