Skip to content

Log app exit reasons and memory use - #788

Merged
marionbarker merged 1 commit into
devfrom
feature/exit-diagnostics
Oct 23, 2026
Merged

marionbarker merged 1 commit into
devfrom
feature/exit-diagnostics

Conversation

@bjorkert

Copy link
Copy Markdown
Member

Some users still see LoopFollow die shortly after going to the background with Silent Tune running, and the log can't tell whether iOS killed it for memory, it crashed, or it was swiped away. This logs MetricKit exit counts and crash diagnostics when iOS delivers them (at most once a day), adds a log line in applicationWillTerminate, and adds the memory footprint and remaining memory to the "App moved to background" line.

MetricKit exit counts and crash diagnostics are written to the log when iOS delivers them. The app also logs when it is about to terminate, and the background log line includes the memory footprint and the memory left before the limit.

@marionbarker marionbarker left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve by test. Did a quit, then restart and shared log, see

[14:51:10] [General] App will terminate (memoryFootprint=43 MB, memoryAvailable=2054 MB)

in shared log.

Assuming the rest works as expected.

@marionbarker
marionbarker merged commit 9b9124c into dev Oct 23, 2026
1 check passed
@marionbarker
marionbarker deleted the feature/exit-diagnostics branch October 23, 2026 21:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants