Handling Network process crash

[sjames1958]

We have recently moved from an old version of CEF running as a single process to the latest multiple process CEF (84).
I am working on making sure that our app is resilient to process failures. For the renderer we get an event in the browser and can handle that.
For the GPU and network processes those are restarted automatically. All seems great. However, network requests that are in flight when the
network process fails hang. Is there any mechanism in CEF to be able to 1) be notified in the browser process of the network process failure or 2)
get some notification that a network requests failed due to network process failure?

This is on macOS and windows 32 bit.

[magreenblatt]

network requests that are in flight when the
network process fails hang

How are you testing or reproducing a crashing network process? Does this hang problem reproduce with Google Chrome?

[sjames1958]

The hanging happens in the C++ Code, not in the browser, so duplicating in Chrome doesn't seem the same.
I am killing the process using kill function - this is on macOS, just FYI

[magreenblatt]

The hanging happens in the C++ Code, not in the browser, so duplicating in Chrome doesn't seem the same.

Were you able to identify where (what function, etc) is causing the network requests to hang?

[sjames1958]

No, we just never receive the OnRequestComplete callback after the process is restarted.