Using disable-crashpad-for-testing causing chromium process timeout

[Steve]

Hello team,

I'm launching Chromium binary in a Java service on Linux, and each new request to the service will cause it to launch a new Chromium process, not ideal but that's the current setup. 

So I've noticed that with the latest Chromium version update, there are a couple more child processes get created, mainly the ones related to crashpad handler as such:

chrome_crashpad_handler --monitor-self --monitor-self-annotation=ptype=crashpad-handler

chrome_crashpad_handler --no-periodic-tasks --monitor-self-annotation=ptype=crashpad-handler

However, when i try to disable it by using: disable-crashpad-handler-for-testing flag, I observed the chromium server will just. timeout while serving a new request as such:

com.github.kklisura.cdt.services.exceptions.ChromeDevToolsInvocationException: Timeout expired while waiting for server response.

And I'm also using --single-process, but if I don't use --disable-crashpad-handler-for-testing, renderer processes will still get created with crashpad-pid along with the two crashpad process.

The same program works fine on Mac with --disable-crashpad-handler-for-testing.

Here are the list of flags I'm using, could you please help me understand why it could cause such issue? Thanks.

--headless

--no-sandbox

--no-zygote

--disable-breakpad

--disable-crash-reporter

--single-process

--disable-crashpad-for-testing

Best,

Steve