Home Dashboard Directory Help
Search

Visual Studio 2012 crash after change the code view layout by Ximing Cheng


Status: 

Closed
 as Won't Fix Help for as Won't Fix


1
0
Sign in
to vote
Type: Bug
ID: 767129
Opened: 10/11/2012 6:03:37 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

When I use Visual Studio 2012, if I change the code view layout, such as I drop a code view window to the left of the currrent code view window, the left is the header file and the right is cpp code file, so that I can have a good view of one class, but after a few minutes, the Visual Studio crashes! I have tried for several times, each when I change the layout, the Visual Studio crashed!
Details
Sign in to post a comment.
Posted by Ximing Cheng on 10/12/2012 at 11:25 PM
I upload the dump files on another issue feedback, please check from http://connect.microsoft.com/VisualStudio/Feedback/details/767292#details
to get the dump files.
Thanks!
Posted by Microsoft on 10/11/2012 at 11:18 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, as well as
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 10/11/2012 at 6:52 PM
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.