Breadcrumbs are not saved in the event on a native crash

[michalzaq12]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Electron SDK Version

4.15.1

Electron Version

26.0.0

What platform are you using?

Windows

Link to Sentry event

No response

Steps to Reproduce

.

Expected Result

The event breadcrumb context should be the same as when the error occurred.

Actual Result

Breadcrumbs are not saved in the event on a native crash, which causes incorrect application context and makes debugging difficult.

[timfish]

What tags was this event sent with?

The Electron SDK has offline support so that if sending of events fails, they are retried later which can give a time difference between occurrence and received.

[michalzaq12]

Tags:

The Electron SDK has offline support so that if sending of events fails, they are retried later which can give a time difference between occurrence and received.

I understand, but when you try to send the event again, the context (breadcrumbs) should not be overwritten.

[timfish]

event.process: browser suggests that this minidump was picked up at application startup. Crashes in the Electron main process (browser) cause the application to terminate so we send these on next app start using saved context if there is any.

It looks like the breadcrumbs there are from the subsequent app start. I'll need to look into this.

[timfish]

When updating the Electron SDK to use the latest Sentry JavaScript SDKs, I simplified how the scope is applied to events.

I added some extra breadcrumbs to the native main tests (#812) and they appear to be as expected so the scope changes might have fixed whatever issues there were before.