-
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
Do not call SignalSession on invalid session IDs #92431
Conversation
/backport to release/8.0-rc2 |
Started backporting to release/8.0-rc2: https://github.com/dotnet/runtime/actions/runs/6268145663 |
src/libraries/System.Private.CoreLib/src/System/Diagnostics/Tracing/EventPipeEventDispatcher.cs
Show resolved
Hide resolved
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.
We should close the potential race between EventPipeInternal.SignalSession(m_sessionID) and EventPipeInternal.Disable(sessionID) by grabbing m_dispatchControllLock around call to EventPipeInternal.Disable(sessionID).
Fixes #92098
Fixes #92236