You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While it is possible to filter out events where DumpWithoutCrashing is the cause, these events still count against the crash free rate for sessions.
Currently it is not possible to conditionally update sessions where a crash is percieved to have happened (even though it may or may not be percieved by the end user of the app).
Solution Brainstorm
In JS SDKs typically you can prevent session updates or manually revert updates to a session where the last event was dropped in an event processor.
Given how Main Process sessions are stored to disk this is not as simple in Electron.
The text was updated successfully, but these errors were encountered:
It looks like it might be a means for Chromium to collect minidumps for specific things that they're trying to debug and get more information for and these shouldn't make it into stable builds 🤔
Do we have symbolicated stack traces for where in Chromium these are getting triggered from?
Perhaps Electron can exclude these from their build or one hasn't been correctly flagged in the chromium source and has made it into stable. It's probably worth opening an issue upstream with Electron with a full stack trace and posing the question?
Problem Statement
Related to: #722 (comment)
While it is possible to filter out events where DumpWithoutCrashing is the cause, these events still count against the crash free rate for sessions.
Currently it is not possible to conditionally update sessions where a crash is percieved to have happened (even though it may or may not be percieved by the end user of the app).
Solution Brainstorm
In JS SDKs typically you can prevent session updates or manually revert updates to a session where the last event was dropped in an event processor.
Given how Main Process sessions are stored to disk this is not as simple in Electron.
The text was updated successfully, but these errors were encountered: