Currently it's not possible to catch certain types of failures e.g. heap corruptions, CFG failures, stack canary corruption. 

This is because these typically result in a 'fastfail' exception, described in two places in MSDN:

__fastfail intrinsic - https://docs.microsoft.com/en-us/cpp/intrinsics/fastfail
RaiseFailFastException - https://msdn.microsoft.com/en-us/library/windows/desktop/dd941688.aspx

Note: These seem to behave differently, see https://bugs.chromium.org/p/crashpad/issues/detail?id=133#c3

Note: __fastfail behavior seems to vary depending on compiler (more research here is needed).

We should probably start by being able to artificially generate these types of exceptions. Perhaps consideration should be given to disabling HeapEnableTerminationOnCorruption on a certain percentage of canary users to gauge how many of these corruptions are happening.

This is also tracked by CrashExitCodes on Windows, for child processes only. I do not believe we have a way of accurately tracking this for Browser process.