workspace.OpenSolutionAsync locked after update code analysis libraries on vs 17.14

[cgamberini]

On vs17.14 my code analysis library did not work, so i updated the libraries to the last version as below:

<PackageReference Include="Microsoft.Build.Locator" Version="1.9.1" />
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" Version="4.14.0" />
<PackageReference Include="Microsoft.CodeAnalysis.CSharp.Workspaces" Version="4.14.0" />
<PackageReference Include="Microsoft.CodeAnalysis.Workspaces.MSBuild" Version="4.14.0" />
<PackageReference Include="Microsoft.Extensions.Configuration" Version="9.0.5" />
<PackageReference Include="Microsoft.Extensions.Configuration.FileExtensions" Version="9.0.5" />
<PackageReference Include="Microsoft.Extensions.Configuration.Json" Version="9.0.5" />
<PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="9.0.5" />
<PackageReference Include="Newtonsoft.Json" Version="13.0.3" />
<PackageReference Include="NuGet.Frameworks" Version="6.14.0" />
<PackageReference Include="NuGet.ProjectModel" Version="6.14.0" />
<PackageReference Include="System.Security.Cryptography.Pkcs" Version="9.0.5" />

now if i call await workspace.OpenSolutionAsync(solutionFilePath); it does not return, in the console there are no errors.

downgrading net sdk using old version this code does not solve the problem.

MSBuildLocator.RegisterMSBuildPath("C:\Program Files\dotnet\sdk\8.0.313");

any suggestions?

NB. solutionFilePath target an ASP.NET MVC application build with .NET framework 4.7.2

Thanks

[jasonmalinowski]

Microsoft.Build.Locator is no longer needed for newer versions of MSBuildWorkspace, so you can delete that.

Otherwise if you can take a memory dump of the hung process (and any child processes), we can look at those further. File a feedback ticket on Visual Studio Developer community and attach any dump files to that. Include a link over here so I can find it and then I can take a look.

[cgamberini]

i opened a ticked on developer community: https://developercommunity.visualstudio.com/t/workspaceOpenSolutionAsync-locked-after/10916274, in the linked issue i attached the dump of the process

[jasonmalinowski]

@cgamberini So when you're hitting the hang, you should see that your process has a child process named Microsoft.CodeAnalysis.Workspaces.MSBuild.BuildHost.exe -- can you share a dump of that too? For a bunch of reasons we do the actual processing of the build in another process, and I see your process has called out to that and is just waiting for a response.

[cgamberini]

@jasonmalinowski attach dump file in comment gave me errors, so i uploaded on filebin: https://filebin.net/xvnelnot7uf2mu11

[jasonmalinowski]

Thanks for the dump -- that was quite helpful. The problem here is two things doing not great things interacting badly:

1. Your build is using BundlerMinifier; a build task there is logging directly to the console rather than through any MSBuild mechanism.
2. We were launching the BuildHost processes redirecting standard output. We originally were using this as a way to communicate with it; we moved to a pipe, but left the redirection in place...and now nothing was reading.

So eventually BundlerMinifier was writing enough that the stream got full, and since we weren't flushing it, it'd deadlock.

[cgamberini]

Thanks @jasonmalinowski , the problem will be solved in next release?

As workaround i have to temporary disable BundlerMinifier?