Alex Rudenko
Alex Rudenko
Here is some additional documentation on sandbox architecture in Chromium https://chromium.googlesource.com/chromium/src/+/HEAD/docs/design/sandbox.md#Sandbox-Windows-architecture
Interesting, so it is crashing inside the browser's network service. Unfortunately, I do not know further details. Does it also crash if you just run a headless screenshot command: `path\to\chrome.exe...
The command `path\to\chrome.exe --headless=new --screenshot https://example.com` does not use Puppeteer in any way and launching Chrome this way is somewhat similar to how Puppeteer itself launches Chrome. So it does...
I find an older issue for "Failed to encrypt" https://issues.chromium.org/issues/40281493#comment23 Not sure if it could be applicable here?
Maybe adding the following args to chrome.exe invocations `--enable-logging --v=1` would provide more details.
You need to include `--screenshot` to make sure a headless command is run to capture a screenshot. Otherwise, it is expected for the browser to just remain open. Errors might...
then it looks like `--enable-features=NetworkServiceInProcess2` should make it work for you?
I think it's worth filing it. NetworkServiceInProcess2 is not available on all platforms and AFAIK it is mostly only used for Android WebViews. I would say Chrome should probably run...
Blocked by https://crbug.com/358515466
I think we can merge the changelog and post the same for both, it would be great.