Generate crash report on macOS if memory is corrupted

Version: 16.0.3068

(I just upgraded to 16.0.3069 and has not reproduced this issue, I will update if it happens again)

I encountered memory corruption errors when I close multiple glyph views using command + W too fast after adding new glyphs. Unlike most other mac Apps, FC will then quit and does not prompt the OS to send the crash report. It seems to me that there is something in the main process that have caught the crash and it does not propagate to the OS level.

If the crash report is helpful, consider generate one so that I can attach the crash report when reporting such bugs.

My current workaround is to the save project whenever a new glyph is added.