Reporter | Joe White (joewhite) |
---|---|
Created | Apr 18, 2011 9:43:12 PM |
Updated | Dec 30, 2011 7:15:31 PM |
Resolved | Dec 28, 2011 10:52:25 PM |
Priority | Show-stopper |
Type | Bug |
Fix versions | 6.1.1 |
State | Fixed |
Assignee | Sergey Coox (coox) |
Subsystem | No subsystem |
Affected versions | 6.0 |
Fixed in build | No Fixed in build |
After I upgraded to the latest ReSharper nightly build (6.0.2134.37), I got an R# tray icon, with a balloon hint: "ReSharper Feedback - Help us improve ReSharper!"
When I clicked on the balloon, Visual Studio locked up. Any time I tried to click on Visual Studio, I got its pop-up "Delay Notification" dialog, saying: "Microsoft Visual Studio is waiting for an operation to complete. If you regularly encounter this delay during normal usage please report this problem to Microsoft. Please include a description of the work you were doing in Microsoft Visual Studio and when possible instructions on how to reproduce this delay. If Microsoft Visual Studio is waiting on another application you can switch to that application now, or you can continue waiting for this application to complete."
This dialog had 3 buttons: "Switch To...", "Continue Waiting", and "Cancel Operation". The first two just closed the dialog without improving the situation (the next click on VS would bring the dialog back). The third was disabled.
Interestingly, the Visual Studio UI only updated while this dialog was up. If I clicked onto another application, the VS dialog disappeared, and the VS UI stopped repainting: the animation froze in the "Errors in Solution" window, and the text stopped updating to show how many files it had analyzed. As soon as I clicked on VS again, the dialog reappeared and the screen started updating again – but of course I couldn't do anything, because the "Delay Notification" dialog was in the way.
I was never able to get the VS dialog to go away, and of course the dialog was blocking me from using Visual Studio. I eventually had to use Process Explorer to kill the devenv process tree.
When I opened Visual Studio again, the tray icon reappeared. I clicked the icon this time (instead of the balloon) and VS locked up again, so I don't think it was a fluke when it happened the first time.
When I clicked on the balloon, Visual Studio locked up. Any time I tried to click on Visual Studio, I got its pop-up "Delay Notification" dialog, saying: "Microsoft Visual Studio is waiting for an operation to complete. If you regularly encounter this delay during normal usage please report this problem to Microsoft. Please include a description of the work you were doing in Microsoft Visual Studio and when possible instructions on how to reproduce this delay. If Microsoft Visual Studio is waiting on another application you can switch to that application now, or you can continue waiting for this application to complete."
This dialog had 3 buttons: "Switch To...", "Continue Waiting", and "Cancel Operation". The first two just closed the dialog without improving the situation (the next click on VS would bring the dialog back). The third was disabled.
Interestingly, the Visual Studio UI only updated while this dialog was up. If I clicked onto another application, the VS dialog disappeared, and the VS UI stopped repainting: the animation froze in the "Errors in Solution" window, and the text stopped updating to show how many files it had analyzed. As soon as I clicked on VS again, the dialog reappeared and the screen started updating again – but of course I couldn't do anything, because the "Delay Notification" dialog was in the way.
I was never able to get the VS dialog to go away, and of course the dialog was blocking me from using Visual Studio. I eventually had to use Process Explorer to kill the devenv process tree.
When I opened Visual Studio again, the tray icon reappeared. I clicked the icon this time (instead of the balloon) and VS locked up again, so I don't think it was a fluke when it happened the first time.