[Bug]: MSB4242: SDK Resolver Failure due to System.Threading.AbandonedMutexException

[kartheekp-ms]

NuGet Product Used

dotnet.exe

Product Version

SDK 6.0.402

Worked before?

No response

Impact

I'm unable to use this version

Repro Steps & Context

Tracking issue for dotnet/sdk#28488. Essentially, this issue can be hit if solution has multiple projects trying to download custom SDKs using NuGet resolver functionality.

Verbose Logs

No response

[kartheekp-ms]

Same error is reported in the following 2 GitHub action runs.

• https://github.com/vezel-dev/cathode/actions/runs/3239525805/jobs/5309017199#step:4:1
• https://github.com/vezel-dev/zig-sdk/actions/runs/3239510618/jobs/5308984814#step:4:1

[kartheekp-ms]

Sorry for the inconvenience caused by this bug. For folks who are hitting this issue, as a workaround, would it be possible to execute dotnet nuget --version command before running the restore. In that way we don't hit the race condition that is causing these failures intermittently.

[alexrp]

I just ran into another failure that seems like it could be related (this is with the aforementioned workaround applied): https://github.com/vezel-dev/niru/actions/runs/3260762897/jobs/5354602659#step:4:15

Package "sourcelink" failed to restore, due to Microsoft.DotNet.ToolPackage.ToolPackageException: The tool package could not be restored.
   at Microsoft.DotNet.Tools.Tool.Install.ProjectRestorer.Restore(FilePath project, PackageLocation packageLocation, String verbosity)
   at Microsoft.DotNet.ToolPackage.ToolPackageInstaller.InstallPackageToExternalManagedLocation(PackageLocation packageLocation, PackageId packageId, VersionRange versionRange, String targetFramework, String verbosity)
   at Microsoft.DotNet.Tools.Tool.Restore.ToolRestoreCommand.InstallPackages(ToolManifestPackage package, Nullable`1 configFile)

This one seems rare - it's the first time I've seen it since applying the workaround and it didn't happen on a subsequent run.

[breidikl]

The workaround has been working in our environment so far, thanks.

[VemundH]

I initially reported here: https://developercommunity.visualstudio.com/t/NuGet---race-condition-NuGetCommonMigr/10175710
Looks like the same issue