--disable-crashpad-for-testing propagation to subprocesses

[James]

Is forwarding --disable-crashpad-crashpad-for-testing to subprocesses a sensible thing to do? At the moment it isn't propagated, and there is no way I can find to prevent subprocesses launching crashpad handlers, which is what I want to do.

Background:

I'm using chrome for testing with puppeteer (--headless=new), and ultimately I'm trying to run it in a constrained environment where namespace sandboxes and ptrace attach are not possible. (Things somewhat work, but are unreliable with --single-process)

I suspect that crashpad is causing some of my problems, and I've tried to disable it using ----disable-breakpad (which puppeteer sets by default),  --disable-crash-reporter, and --disable-crashpad-for-testing but in all cases still get chrome_crashpad_handler processes starting

I've re-built chrome with the disable-crashpad-crashpad-for-testing switch forwarded to the renderer, gpu, and utility subprocesses, and this seems to fix things in combination with --no-zygote. Without --no-zygote some extra guards to respect the flag are needed as well. Still re-building to test in the actual target environment just now.