[WIP] Adding OOM Diagnostics to GCStats and the Events View#2156
Draft
mrsharm wants to merge 6 commits intomicrosoft:mainfrom
Draft
[WIP] Adding OOM Diagnostics to GCStats and the Events View#2156mrsharm wants to merge 6 commits intomicrosoft:mainfrom
mrsharm wants to merge 6 commits intomicrosoft:mainfrom
Conversation
mrsharm
changed the title
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.
This PR adds a separate section for OOM details emitted as a dynamic event from the runtime.
Example of the details (if an OOM exists in the trace) in GCStats:
Interpretation of the Dynamic Event in the Events View:
