VS 11 RC1: XDesProc.exe crashed with InvalidOperationException - by flöle

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 750710 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 6/25/2012 6:31:54 AM
Access Restriction Public

Description

When resizing a WPF control in the designer, XDesProc.exe crashed with an InvalidOperationException.

I attached the event log data (stack trace) and can also upload a mini dump if you provide me with a password for uploading a file in private. (Note: Uploading such large files with the Feedback Tool does not work.)
Sign in to post a comment.
Posted by Microsoft on 7/13/2012 at 12:12 PM
Hi Florian,
         We are unable to repro this on our end. However we have opened a bug on our end to use your dump and stack trace to figure out the issue. Unfortunately this wont make it RTM but if we find the root cause we hopefully might be able to get it for a service update. As always we deeply appreciate your feedback.
Regards
Harikrishna Menon
Program Manager
Posted by Microsoft on 7/12/2012 at 11:39 PM
Thank you for submitting feedback on Visual Studio 11 and .NET Framework. Your issue has been routed to the appropriate VS development team for review. We will contact you if we require any additional information.
Posted by flöle on 7/4/2012 at 3:19 AM
File has been uploaded.
Posted by Microsoft on 7/4/2012 at 1:55 AM
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 Dump As Minidump with 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... 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 http://blogs.msdn.com/debugger/archive/2009/12/30/what-is-a-dump-and-how-do-i-create-one.aspx

Please package your files into a zip file and name the zipped file Feedback-750710.zip.
You can upload the file to workspace:

https://sftus.one.microsoft.com/choosetransfer.aspx?key=e753bd2d-72ec-482e-83b0-bbcbeb3417b4
Password: APY9sO53lGh

It would be greatly appreciated if you could provide us with that information as quickly as possible.

Thanks again for your efforts and we look forward to hear from you.
Posted by flöle on 6/28/2012 at 2:23 AM
I already said "and can also upload a mini dump if you provide me with a password for uploading a file in private."

And I also said "Uploading such large files with the Feedback Tool does not work". In fact, attaching any files to existing issues does not work.

So please provide me with a method for uploading other than using the feedback tool and I'll give you the dump.
Posted by Microsoft on 6/28/2012 at 1:17 AM
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 or hang, control should go to the second instance of VS.
9. In the second instance click Debug | Save Dump As Minidump with 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... 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 http://blogs.msdn.com/debugger/archive/2009/12/30/what-is-a-dump-and-how-do-i-create-one.aspx

You can upload the file with the Visual Studio 12 Feedback tool. You can get detailed steps about how to use Visual Studio 12 Feedback tool at http://visualstudiogallery.msdn.microsoft.com/f8a5aac8-0418-4f88-9d34-bdbe2c4cfe72

It would be greatly appreciated if you could provide us with that information as quickly as possible.

Thanks again for your efforts and we look forward to hear from you.
Posted by Microsoft on 6/25/2012 at 6:49 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)