A significant number of crashes we receive are caused by faulty hardware with broken memory being a common cause of heap corruption. If we could add a simple form of user-space memory testing (à la memtester) to the exception handler we might be able to identify faulty machines and flag crash reports accordingly, inform the user or both.

This bug is meant to track the implementation of the checking itself.

I'm changing the title to reflect the fact that we'll move all crash generation out-of-process so what we could do is the following: take the minidump as usual and report it to the main process, use the crash generation process to map the memory of the crashed process, scan it with a memtest algorithm and flag the crash reports if we find bad bits.

There's a user-space memory tester called memtester which we could take inspiration from (or maybe reuse?).

This might also be of interest: https://memtest.org/readme#memory-testing-philosophy

I was speaking with @gcp and suggested that it could be a good idea to make the badram scanning a separate library so that it can be used both by the crash reporter and by some future in-process bad ram scanning. I filed bug 1897102 before I remembered this bug. I think it's still good to have separate bugs for the library and then the integration in the crash reporter.