[release/10.0] Fix removing module from appdomain in DB_IPCE_UNLOAD_MODULE event#124241
Merged
steveisok merged 1 commit intorelease/10.0from Feb 11, 2026
Merged
Conversation
Contributor
|
Tagging subscribers to this area: @steveisok, @tommcdon, @dotnet/dotnet-diag |
hoyosjs
approved these changes
Feb 11, 2026
Member
|
/ba-g Too many known issues to list |
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
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.
Backport of #123931 to release/10.0
/cc @hoyosjs @tommcdon
Customer Impact
When loading and unloading an Assembly multiple times in new AssemblyLoadContexts Visual Studio will abruptly end debugging before program completion with the following error:
Originally reported via Visual Studio feedback item Fatal error encountered when debugging .net 10 app using collectible assemblies in VS2026, then moved to GH issue #123930.
Regression
Regression from .NET 9, introduced in .NET 10 on #117224 and was a missed case when attempting to address the issue in #118414.
Testing
Validated with customer's reproducible test case on #123930
Risk
Low. The debugger module caches uses the module as the hash key rather than the assembly. This was a missed case when fixing #118414 where we were still incorrectly using the assembly as the lookup key.