Revolutionizing ANR Detection at Sentry
summary
New ANR pipeline switches from a real‑time watchdog to Android’s Application Exit Info API on Android 11+, persisting breadcrumbs, tags and contexts to disk so the next app launch can reconstruct the exact ANR (timestamped fatal event) and avoid duplicates. It parses the system trace with a sys_trace parser (regexes) to produce full thread stacks and deadlock flags, still keeps the watchdog for sub‑5s hangs and plans persisted profiles to link slow functions to ANRs.
AI-written summary · about
chapters (8)
- 0:00Introduction to Sentry
- 3:11What is an ANR?
- 6:24ANR detection approaches
- 9:52Limitations of old ANR detection
- 10:56New ANR detection at Sentry
- 14:27Enriching ANR events
- 15:31Parsing system traces
- 16:56Future improvements
related talks
22mANR overview at Uber + Leveraging ApplicationExitInfo API
29mHow the Android Framework Monitors, Processes, and Triggers ANRs
39mWhere Is Your ANR Coming From? — Diagnosing How It Occurs and Prescribing Remedies by Symptom
12mUnderstanding and debugging ANR's (Android Not Responding)
29mWhy ANRs are Hard to Solve and What You Can Do to Make it Easier
29mHow the Android Framework Monitors, Processes, and Triggers ANRs
22mEverything you ever wanted to know about error handling in Android
24mMake the Most of Android Vitals