1966720 - Make the heap corruption vectored exception-handler more robust (or use WER instead)

Status: NEW

(Toolkit :: Crash Reporting, defect)

Description

[Gabriele Svelto [:gsvelto]]

The handler for heap corruption exceptions (see bug 1633052) relies on several Windows function which can make allocations, and given tha the heap is corrupted (well, duh) these can trigger a recursive exception (see bug 1956290). In order to fix this problem we can try two approaches: move crash generation entirely out-of-process so that we don't need to do any relevant processing in the handler itself. If that doesn't work we might remove the handler entirely and rely on WER to catch those exceptions, but then we'd need to fix bug 1874886 first.

Comment 1

[BugBot [:suhaib / :marco]]

The severity field is not set for this bug.
:gsvelto, could you have a look please?

For more information, please visit BugBot documentation.