Minidump is not picked up after webContents.forcefullyCrashRenderer()

[timfish]

As per this comment, cc @Cefold

After webContents.forcefullyCrashRenderer() event, there was a minidump under pending folder, but it seems that Sentry cannot find it. It will upload it until next app restart, thus event.process will be classified as browser instead of renderer.

It looks like this is caused by the fact that the minidump ends up in the pending directory until the app restarts on macOS.

[timfish]

It's worth noting that Electrons behaviour here differs between platforms.

• On Windows and Linux forcefullyCrashRenderer() results in { reason: 'crashed' } with the minidump in the regular location
• On macOS forcefullyCrashRenderer() results in { reason: 'exited' } with the minidump in the pending directory

This means on Windows and Linux there is no way to determine if a minidump came from a regular crash or a forced crash. One possible way to mitigate this would be to manually set tags before calling forcefullyCrashRenderer.