Conversation
when a debugger is attached, NotifyOfCrossThreadDependency will freeze the thread to send notification to the debugger. Because this NoMessagePumpSynchronizationContext is heavily used, including nested inside code holding the JTF lock, this leads the process being debugged becomes extremely slow when JTF is heavily used.
AArnott
approved these changes
Sep 17, 2025
| { | ||
| get | ||
| { | ||
| // Callers of this method are about to take a private lock, which tends |
Member
There was a problem hiding this comment.
You could avoid the debugger hangs by adding [DebuggerBrowsable(DebuggerBrowsableState.Never)] to the property.
lifengl
deleted the
dev/lifengl/removeNotifyOfCrossThreadDependencyInSynchronizationContext
branch
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
2 participants
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.
When a debugger is attached, NotifyOfCrossThreadDependency will freeze the thread to send notification to the debugger. Because this NoMessagePumpSynchronizationContext is heavily used, including nested inside code holding the JTF lock already, this logic to call this debugger notification in a very common code path leads the process being debugged becomes extremely slow when JTF is heavily used.