fix(telemetry): drop App-Hang reports from memory-starved machines#197
Merged
Conversation
The recent ANR reports — including the regressed BURROW-N (687 events / 102 users) and the whole newest BURROW-5x cluster — are CoreAnimation display-commit stalls on macOS 27 betas with only tens of MB of free RAM: the OS thrashing the render path under memory pressure, not a Burrow defect. The specific main-thread blockers were already moved off-main in 0.8.1. Add a beforeSend filter that drops App-Hang events when the device reports < 150 MB free memory; real hangs on healthy machines still report. Conservative: if free memory can't be read, the event is kept.
This was referenced Jun 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The current Sentry App-Hang (ANR) feed is dominated by environmental stalls, not Burrow defects:
CA::Transaction::flushdisplay-commit stall; its latest event is macOS 27 beta, 85 MB free.BackupStatus.lastBackupDaysAgo, Doctor probes,AppIcon.image, PostHog) are already off-main as of 0.8.1 — verified in current code.So a >2 s freeze on a machine with tens of MB free is the OS thrashing render under memory pressure. This adds a
beforeSendfilter dropping App-Hang events when the device reports < 150 MB free; genuine hangs on healthy machines still report. Conservative — if free memory can't be read, the event is kept.Verified: Debug build succeeds (the Sentry
EventAPI usage type-checks).