Fix missing context for crash, OOM, and app hang errors #1079
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.
Goal
Include the
context
value in crash, OOM, and app hang errors.Changeset
context
is now stored in thestate
metadata (which is added to KSCrashReports and persisted to be available at next launch.)App hang events now have the
context
applied.OOM events now take the context from the previously persisted state metadata.
Crashes now take the
context
from the state metadata included in the KSCrashReport.Made
config.context
atomic
because it could be written to and read from arbitrary threads.Testing
Amended E2E scenarios to verify presence of
context
and ran them locally.