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
When an app hang leads to a watchdog termination, we can report this as a fatal app hang. When the SDK detects a fully blocking app hang, it needs to store the app hang to disk and wait for the app to recover from the app hang. When the app doesn't recover, the SDK must send the app hang as a fatal on the next app launch. When the app recovers from the app hang, then it must send it as a fully blocking app hang. The downside of this approach is that app hangs will be reported a bit delayed, which is acceptable.
We must align with Android and report sessions as abnormal when a fatal app hang occurs. For reference: getsentry/sentry-java#2475
This issue is a prerequisite to #3319, because the app hang rate only considers fatal app hangs.
The content you are editing has changed. Please copy your edits and refresh the page.
This PR reports fatal app hangs without session updates, only when the
experimental option enableAppHangTrackingV2 is enabled. Updating the
session will be done in a follow-up PR.
This fixes the first part of GH-4260.
Description
When an app hang leads to a watchdog termination, we can report this as a fatal app hang. When the SDK detects a fully blocking app hang, it needs to store the app hang to disk and wait for the app to recover from the app hang. When the app doesn't recover, the SDK must send the app hang as a fatal on the next app launch. When the app recovers from the app hang, then it must send it as a fully blocking app hang. The downside of this approach is that app hangs will be reported a bit delayed, which is acceptable.
We must align with Android and report sessions as abnormal when a fatal app hang occurs. For reference: getsentry/sentry-java#2475
This issue is a prerequisite to #3319, because the app hang rate only considers fatal app hangs.
Tasks
The text was updated successfully, but these errors were encountered: