Solution skill
Silent browser disconnects in Docker - disable NetworkServiceInProcess2
Complete solution
Shows how to fix silent browser disconnects in Docker - disable NetworkServiceInProcess2. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
If Puppeteer disconnects in Docker with zero errors in the log, launch Chrome with the flag that disables the NetworkServiceInProcess2 feature.
Steps
- If Puppeteer disconnects in Docker with zero errors in the log, launch Chrome with the flag that disables the NetworkServiceInProcess2 feature. That was the maintainer's workaround for this silent-disconnect bug and the reporter confirmed it. One caveat from the thread: the flag can affect network interception features, so if you rely on request interception, test that path explicitly after applying it.
When to use
You are seeing this: That was the maintainer's workaround for this silent-disconnect bug and the reporter confirmed it. Use this skill when you run into "Silent browser disconnects in Docker - disable NetworkServiceInProcess2".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Edge cases
- One caveat from the thread: the flag can affect network interception features, so if you rely on request interception, test that path explicitly after applying it.
Evidence
Source: Issue puppeteer/puppeteer#12257 (closed, 28 comments): the browser silently disconnected in Docker with no error at all. A maintainer (OrKoN) filed the upstream Chromium bug and gave the workaround, which the reporter confirmed works.
Verified resolution: If Puppeteer disconnects in Docker with zero errors in the log, launch Chrome with the flag that disables the NetworkServiceInProcess2 feature. That was the maintainer's workaround for this silent-disconnect bug and the reporter confirmed it. One caveat from the thread: the flag can affect network interception features, so if you rely on request interception, test that path explicitly after applying it.
Source URL: https://github.com/puppeteer/puppeteer/issues/12257
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_DwxoTtKIMxvq-5WoFZDywQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Silent browser disconnects in Docker - disable NetworkServiceInProcess2 <span>— Vectle</span></a>