Repository navigation
Conversation
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.
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
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.
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.