Home Dashboard Directory Help
Search

Visual Studio 2012 XAML Editor keeps crashing by LANDesk SteckDEV


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


1
0
Sign in
to vote
Type: Bug
ID: 794119
Opened: 7/16/2013 7:34:37 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

While working on my WPF MVVM application the instance of Visual Studio keeps crashing. This is very disruputing to my work. This happens about twice a day and I lose any work that has not been saved. I not sure what the reproduce exactly is but like I said it happens multiple times a day and so I can gather any information you need.
Details
Sign in to post a comment.
Posted by Microsoft on 7/29/2013 at 3:33 AM
Hi, given that we have not heard back from you in 7 days. We will go ahead and close this Connect Issue. If you get a chance to review and provide the information requested earlier, you can go ahead and reactivate this issue.
Posted by Microsoft on 7/25/2013 at 10:27 PM
I am currently standing by for an update from you and would like to know how things are going on your end. If you could get back to me at your earliest convenience with information I request, we will be able to make headway towards a resolution. I look forward to hearing from you.
Posted by Microsoft on 7/22/2013 at 1:51 AM
Thanks for your update. However, the file I requested before was dump file. Could you please refer to the following steps to collect a dump file?

1. Start Microsoft Visual Studio 2012 Feedback Tool
2. Select "Add to an existing feedback"
3. Select type: Crash
4. Record a repro: When the dialog box appears, select the running Visual Studio instance for which you want to show the steps that cause a crash. When the crash occurs, click on the "Stop Record" button. After you do this, two files are attached to your bug report - an AutomaticCrashDump.zip file that contains information about the crash and a ReproSteps.zip file that shows the repro steps.
5. Go to C:\Users\<username>\AppData\Local\VSFeedbackTool\Feedbacks\<id>, you can find the dump file. Please zip the file and use "FeedbackID-794119" as prefix of the file name. You can use the following workspace to upload the file:
https://sftus.one.microsoft.com/choosetransfer.aspx?key=59fd01aa-2675-43d0-a611-8edfde5b5bac
Password: 4[mfysk2[$]QM

For more detail, please refer to https://connect.microsoft.com/VisualStudio/content/content.aspx?ContentID=26698

Thanks,
Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 7/19/2013 at 6:16 AM
Thanks for your update. However, the file I requested before was dump file. Could you please refer to the following steps to collect a dump file?

1. Start Microsoft Visual Studio 2012 Feedback Tool
2. Select "Add to an existing feedback"
3. Select type: Crash
4. Record a repro: When the dialog box appears, select the running Visual Studio instance for which you want to show the steps that cause a crash. When the crash occurs, click on the "Stop Record" button. After you do this, two files are attached to your bug report - an AutomaticCrashDump.zip file that contains information about the crash and a ReproSteps.zip file that shows the repro steps.
5. Go to C:\Users\<username>\AppData\Local\VSFeedbackTool\Feedbacks\<id> to fine the dump file. Please zip the file and use "FeedbackID-794119" as prefix of the file name. You can use the following workspace to upload the file:
https://sftus.one.microsoft.com/choosetransfer.aspx?key=59fd01aa-2675-43d0-a611-8edfde5b5bac
Password: 4[mfysk2[$]QM

For more detail, please refer to https://connect.microsoft.com/VisualStudio/content/content.aspx?ContentID=26698

Thanks,
Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 7/16/2013 at 11:33 PM
Thanks for your feedback. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a dump file and call stack so that we can conduct further research?

Visual Studio now has an extension called Microsoft Visual Studio 2012 Feedback Tool, available on the VS gallery(http://visualstudiogallery.msdn.microsoft.com/f8a5aac8-0418-4f88-9d34-bdbe2c4cfe72).

The extension allows you to
1. upload files,
2. collect trace and dump files
3. collect steps while you're repro'ing the issue
4. SQM logs about VS extensions installed
5. System details (in DxDiag output)

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 7/16/2013 at 7:51 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)
Sign in to post a workaround.
File Name Submitted By Submitted On File Size  
VsInfo.xml (restricted) 7/17/2013 -
WERB5D7.tmp.appcompat.txt (restricted) 7/17/2013 -
UploadSummary-130717180146.xml (restricted) 7/17/2013 -
DxDiagOutput.txt (restricted) 7/17/2013 -
SolutionFingerprint.48.html (restricted) 7/17/2013 -