-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[release/8.0] Remove public provider from rundown session #92048
Conversation
Co-authored-by: Aleksey Kliger (λgeek) <akliger@gmail.com>
@davmason please fill out the template, get a code owner sign-off, and add the |
@jeffschwMSFT can we get your autograph? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approved. please get a code review. once ready this can be merged
@lateralusX can you please sign-off the backport too? Or alternatively @lambdageek @noahfalk @brianrob @MichalStrehovsky who were added as reviewers in the main PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Backport of #91383 to release/8.0
/cc @davmason
Customer Impact
When we created EventPipe we mimicked the rundown logic from Perfview, which enabled the public Microsoft-Windows-DOTNETRuntime provider during rundown to support pre v4 runtimes. This has the unintended side effect of introducing unwanted events in to traces - e.g. if a user configured a trace without GC events we would have GC events emitted during rundown. This has the potential to confuse some analysis tools.
Testing
A CI run with a change that would failfast if we saw a non-rundown provider being fired on a rundown thread, plus manual verification with the dotnet-* tools.
Risk
Low - we could not identify any non rundown events that are emitted or any tools that expect those events to be emitted during rundown.
IMPORTANT: If this backport is for a servicing release, please verify that:
The PR target branch is
release/X.0-staging
, notrelease/X.0
.If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.