Visual Studio 2010 Crashes when docking windows in a second display - by mattj1856

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 581747 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 7/30/2010 1:56:27 PM
Access Restriction Public


I have a dual display setup.  Visual studio crashes consistantly when I try to bring the find/replace panel and the results panel to a second monitor.  No project or solution needs to be loaded to reproduce the problem.

See steps to reproduce below.  Interesting thing is that it only crashes the first time when docking left/right.  Top/bottom doesn't crash at first, unless you then move it and dock again, then it crashes the second time.

Either way, it seems to be quirk in the window docking part of VS.
Sign in to post a comment.
Posted by mattj1856 on 2/24/2011 at 1:13 PM
I can still reproduce this in SP1 Beta. Can you confirm whether or not the fix was included?

Posted by Microsoft on 8/24/2010 at 1:58 PM
We have fixed this issue in the next VS version and will consider porting this to SP1 if it's part of our top-rated issues.

Visual Studio Platform Team
Posted by Microsoft on 8/3/2010 at 1:46 AM
Hi mattj1856,

We have got your file.We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you.
Posted by mattj1856 on 8/2/2010 at 12:43 PM
Dump taken and attached to this issue, and also uploaded as requested. Also, when the crash occurs while I've got the debugger attached, I see the exception thrown as follows:

An unhandled exception of type 'System.ArgumentOutOfRangeException' occurred in Microsoft.VisualStudio.Shell.ViewManager.dll

Additional information: FloatingWidth and FloatingHeight must be non-negative.

In this particular case, the crash didn't occur when I first docked the find panel to the left of the find results, but when I then dragged it off the left side and re-docked it to the right side. Not sure why it's not always the same, but eventually if you move it around enough it will always crash.
Posted by Microsoft on 8/1/2010 at 10:14 PM
Thanks for reporting the issue.
In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

It may help if you provide us with a mini dump file and call stack. You can use the following steps to get a mini dump file:
1. Start Visual Studio.
2. Start another instance of VS.
3. In the second instance click Tools | Attach to Process...
4. In the list of processes locate devenv.exe.
5. Click Select... and explicitly choose 'Native' and 'Managed' code.
6. Click OK and OK to close Select dialog and Attach to Process dialog.
7. Go back to the first instance of VS and repro the crash\hang.
8. Upon the crash\hang, control should go to the second instance of VS.
9. In the second instance click Debug | Save Mini Dump (without heap).

If you are running the VB profile you will not see the Save Dump As menu item. To add this menu item:
a. Select Tools -> Customize
b. Select the Commands tab
c. Select Debug from the “Menu bar” dropdown
d. Click “Add Command…”
e. Select Debug from the Categories list.
f. Find the “Save Dump As” entry in the Commands window.
g. Click OK (the “Save Dump As…[mini dump ](without heap)” command is added to the top of the Debug menu).
h. Click “Close”

You can get detailed steps about how to get the dump file and call stack at

Please name the zipped file
You can upload the file to workspace:
Password: #Tejy))YPc
It would be greatly appreciated if you could provide us with that information as quickly as possible. If we do not hear back from you within 7 days, we will close this issue.

Thanks again for your efforts and we look forward to hearing from you.
Visual Studio Product Team
Posted by Microsoft on 7/30/2010 at 5:10 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(