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]: Browser crashes when a navigational request is aborted using --single-process flag #12195
Comments
This issue has an outdated Puppeteer version: |
|
See https://groups.google.com/a/chromium.org/g/chromium-dev/c/9Nmw91P45wM w.r.t to the discussion about |
This part is causing the issue // Commits in the error page process must only be failures, otherwise
// successful navigations could commit documents from origins different
// than the chrome-error://chromewebdata/ one and violate expectations.
if (should_commit_error_page &&
(navigation_request && !navigation_request->DidEncounterError())) {
DEBUG_ALIAS_FOR_ORIGIN(origin_debug_alias, params->origin);
bad_message::ReceivedBadMessage(
process, bad_message::RFH_ERROR_PROCESS_NON_ERROR_COMMIT);
return false;
} Well, probably not this part exactly, that's where my digging skills ended up ;) The original error message I'm getting says The |
It seems a must for us, otherwise chromium just won't start in an environment such as Lambda. I tried to but failed. |
We can keep the issue open but it is up to the Chromium team to decide if they will support/fix it. Lambda is not really a target environment for the browser. |
I believe |
@heaven would you mind filing a new crbug.com issue with a reproducible example and mentioning the --single-process bug? it looks like the previous was fixed/closed. |
Submitted to https://issues.chromium.org/issues/332736061 |
Got to my Linux machine but I am not able to reproduce this crash on a Linux. Is it only happening on a Lambda? |
I feel bad already each time I hear the word Lambda 🙂 But yes, that's where I see this. |
I also have this in a Docker container using node:21 base image with Debian-packaged Chromium (123.0.6312.86) and (sightly outdated) puppeteer-core ^21.1.1. Using an older image with Chromium 121.0.6167.160 and the same puppeteer version, it seems to work. No Lambda ;P |
@dstapp please provide a reproducible example (Dockerfile?) in the upstream issue. Since puppeteer-core version is the same it is clearly the browser issue. |
Could you try with the latest version (or without the NetworkServiceInProcess2 feature flag)? in another issue, we found that NetworkServiceInProcess2 might cause crashes for some websites. |
Minimal, reproducible example
Error string
bad_message.cc(29)] Terminating renderer for bad IPC message, reason 205
Bug behavior
Background
This upstream bug happens when the
single-process
option is set. In this case, when a navigational request is being aborted the renderer is being killed, which leads to browsed death. This shouldn't happen in a single process mode I believe.I was able to reproduce this with response interceptions as well https://stackoverflow.com/a/78263262/4846702
More details about what is happening https://issues.chromium.org/issues/40058380
Expectation
The browser should keep running when a navigational request is aborted.
Reality
The browser process dies along with the renderer.
Puppeteer configuration file (if used)
No response
Puppeteer version
22.4.1
Node version
20.11.1
Package manager
npm
Package manager version
10.2.4
Operating system
Linux
The text was updated successfully, but these errors were encountered: