Problem closing Visual Studio 2010

I suspect this is related to my Very long load times for the initial view in MVC3 question yesterday, but I also think it counts as a separated issue. I think other developers may experience this problem even without coding for MVC3 etc. After experiencing yet another very long load time, I closed Visual Studio.

I now still have a running devenv开发者_如何学Go process consuming 460MB of memory, and nothing I have tried will kill that process. I have no visible applications open that might be holding onto it, and I can't kill it with Task Manager, nor with PowerShell's kill cmdlet.

I realise this question could be shoe-horned into a SuperUser question, but it is directly related to an anomoly with a development tool, and is very likely closely related to the development process.

According to this you can attach a new instance of visual studio to the hanging one and kill it there.

http://connect.microsoft.com/VisualStudio/feedback/details/544459/cannot-kill-devenv-exe-until-logout

I just killed an instance that hang on "Loading Intellisense" forever and was unkillable by normal means.