-
Notifications
You must be signed in to change notification settings - Fork 782
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ghost processes after initial build #14988
Comments
These mostly look to be MSBuild worker nodes - these stay around on purpose, but they shouldn't be locking any assemblies since those assemblies should be unloaded after a build. If this is causing actual problems you should be able to force them all to shut down with |
Interesting, I am seeing this:
Building the solution again does resolve the problem. |
So, at this point, we don't do anything extra, just a normal |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Apologies for not reporting this sooner but I fear I still found a problem after #14677.
Repro steps
dotnet build Fsharp.Compiler.Service.sln
Get-Process -Name "dotnet" | Select-Object Id,Name,StartTime,CommandLine
Expected behavior
There shouldn't be any lingering dotnet processes after that initial build.
When doing a rebuild or
-c Release
fslex
could be stuck because of a lock.Actual behavior
Known workarounds
Kill all the processes:
Get-Process -Name "dotnet" | Kill
The text was updated successfully, but these errors were encountered: