Skip to content
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

Visual Studio 2017 RC hangs on closing VF# solution #2022

Closed
forki opened this issue Dec 15, 2016 · 13 comments
Closed

Visual Studio 2017 RC hangs on closing VF# solution #2022

forki opened this issue Dec 15, 2016 · 13 comments
Labels
Impact-High (Internal MS Team use only) Describes an issue with extreme impact on existing code. Regression
Milestone

Comments

@forki
Copy link
Contributor

forki commented Dec 15, 2016

Nearly every time I close the VF# solution (sln from this repo here) in VS2017 RC the VS hangs forever on unloading project 50 from 64.

image

Same happens when switching branches.

@cartermp
Copy link
Contributor

I haven't encountered this before - neither on my desktop nor my laptop. Do you have similar behavior in other F# projects with a fair amount of .fsprojs?

@forki
Copy link
Contributor Author

forki commented Dec 16, 2016 via email

@cartermp
Copy link
Contributor

cartermp commented Jan 6, 2017

@forki have you noticed this lately? I still haven't encountered it.

@forki
Copy link
Contributor Author

forki commented Jan 6, 2017

Yes still there

@cartermp cartermp added Area-IDE Project System Impact-Medium (Internal MS Team use only) Describes an issue with moderate impact on existing code. labels Jan 6, 2017
@cartermp cartermp added this to the VS 2017 Updates milestone Jan 6, 2017
@cartermp
Copy link
Contributor

FYI I was able to repro this on a VM. It's inconsistent (could never repro it on my desktop nor my laptop after multiple installations), but now that we have a VM with this repro-ing we can try and get a fix. Unfortunately we're going to have to punt this one for now, but we're calling it out as a known regression ...and thus it has a high priority for us to fix.

@cartermp cartermp added Impact-High (Internal MS Team use only) Describes an issue with extreme impact on existing code. and removed Impact-Medium (Internal MS Team use only) Describes an issue with moderate impact on existing code. labels Jan 20, 2017
@cartermp
Copy link
Contributor

cartermp commented Feb 2, 2017

Just an update: I've been seeing this pretty consistently now with RC3 + VSIX installed. Not sure how that "helped" by making it more common, but at least it's something we can pin down pretty reliably.

@vasily-kirichenko
Copy link
Contributor

Yes, I see it now on RC3. This is what dotTrace shows:

image

Leaving alone the huge portion on native code, Microsoft.CodeAnalysis.Workspace.OnDocumentContextUpdated is actively doing something in a background thread. I'm not sure if it's our issue or Roslyn's. Note that VS loads one CPU code forever.

@vasily-kirichenko
Copy link
Contributor

image

@vasily-kirichenko
Copy link
Contributor

Looks like Roslyn is waiting SemaphoreSlim here http://source.roslyn.io/#Microsoft.CodeAnalysis.Workspaces/Workspace/Workspace_Editor.cs,347
This semaphore can be locked in any of 34 places where it's used :(

@Pilchie @CyrusNajmabadi any ideas how to investigate it further?

@CyrusNajmabadi
Copy link
Member

Is this just a dupe of dotnet/roslyn#14479 ? If so, @dpoeschl has submitted a fix here: dotnet/roslyn#16889

@vasily-kirichenko
Copy link
Contributor

@CyrusNajmabadi yes, looks like it's the same bug. And it looks like the fix is going to RTM?

@CyrusNajmabadi
Copy link
Member

Yup. The fix is going into RTM.

@forki
Copy link
Contributor Author

forki commented Feb 4, 2017

Cool. Would have been a real paint point otherwise. Thanks

@forki forki closed this as completed Feb 4, 2017
@cartermp cartermp modified the milestones: VS 2017 Updates, VS 2017 RTM Jun 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Impact-High (Internal MS Team use only) Describes an issue with extreme impact on existing code. Regression
Projects
None yet
Development

No branches or pull requests

4 participants