Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Suggestion from a work colleague – when VS is very very slow or is hanging:
Open a second copy of VS and attach
its debugger to the first copy. When
the first copy hangs, pause it in the
second copy and look at the call
stack..
I thought it was a cool idea… but would am I missing something here? Are there any pitfalls with this approach? Or does anyone have an even better approach?
This is a completely reasonable way to determine why Visual Studio, or any other application for that matter, is hanging or unresponsive. I used it frequently when I worked on the Visual Studio team.