-
-
Notifications
You must be signed in to change notification settings - Fork 478
chore(android): Mark MemoryLimiter sessions as having exited abnormally (JAVA-687) #6113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
0xadam-brown
wants to merge
2
commits into
feat/memory-limiter-integration
Choose a base branch
from
feat/memory-limiter-session-repair-pipeline
base: feat/memory-limiter-integration
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,22 +5,34 @@ | |
| /** | ||
| * Marker interface for Sessions experiencing abnormal status. | ||
| * | ||
| * <p><b>Note:</b> While this interface applies to the broad category of abnormal exits (meaning any | ||
| * exits that weren't classified as normal terminations or crashes) it currently is exclusively used | ||
| * as a hint marker for Android ANRs (both watchdog and ApplicationExitInfo based). If additional | ||
| * categories of abnormal exits were introduced, all instances of discriminator code (`instanceof | ||
| * AbnormalExit`) should be carefully reviewed for ANR specifics accidentally being applied. | ||
| * <p>Includes exits that were not classified as normal terminations or crashes, such as Android | ||
| * ANRs and MemoryLimiter process deaths. | ||
| * | ||
| * <p><b>Note:</b> Some existing discriminator code (`instanceof AbnormalExit`) is shaped by the | ||
| * historical ANR-only usage of this interface. New implementations should review all of those call | ||
| * sites carefully to ensure ANR-specific behavior isn't applied accidentally. | ||
|
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. (Fyi, I checked those call sites in connection with the work here, and we didn't need to make any changes.) |
||
| */ | ||
| public interface AbnormalExit { | ||
|
|
||
| /** What was the mechanism this Session has abnormal'ed with */ | ||
| @Nullable | ||
| String mechanism(); | ||
|
|
||
| /** Whether the current thread should be ignored from being marked as crashed, e.g. a watchdog */ | ||
| /** | ||
| * Whether the current thread (e.g., a watchdog) should be ignored by the `MainEventProcessor` | ||
| * when deciding which threads should from the current process should be bound to the Sentry event | ||
| * associated with this `AbnormalExit`. | ||
| * | ||
| * <p>This method effectively no-ops for types implementing both {@link AbnormalExit} and {@link | ||
| * Backfillable}, as implementors of `Backfillable` are not sent to the `MainEventProcessor`. | ||
| */ | ||
| boolean ignoreCurrentThread(); | ||
|
|
||
| /** When exactly the abnormal exit happened */ | ||
| /** | ||
| * When exactly the abnormal exit happened. | ||
| * | ||
| * <p>Epoch time in milliseconds, or null. | ||
| */ | ||
| @Nullable | ||
| Long timestamp(); | ||
| } | ||
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.
Uh oh!
There was an error while loading. Please reload this page.