Fix a deadlock in EventSource and CounterGroup #40259
Merged
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.
Fix #40190
A deadlock can occur when the callback encountered in counter.WritePayload() contains a path that contains a EventSource constructor. EventSource constructor tries to take EventSource.EventListenerLock which may already be held by another thread. Simultaneously, the thread that holds to the EventListenerLock can be blocked on s_CounterGroupLock if it calls enable on an EventSource with EventCounter enabled, resulting in a deadlock.
Essentially the only change in this PR is taking out the call to counter.WritePayload(); to out of the scope of s_counterGroupLock. The fields in CounterGroup (both static and non-static) are still read/written inside s_counterGroupLock.
Note: We may need to backport this fix to 3.1.