Visual studio 2013 crashes while parsing big c++ file (2.2Mbytes) - by Jean-Francois Lots

Status : 

  Duplicate<br /><br />
		This item appears to be a duplicate of another existing Connect or internal item.<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 810381 Comments
Status Closed Workarounds
Type Bug Repros 5
Opened 12/1/2013 12:39:21 AM
Access Restriction Public


While opening our VS2010 project, VS2013 consistently crashes while intellisense is parsing one particularly long c++ file. A workaround to open the solution is to disable all intellisense functions. 
This file is simply ignored by intellisense in visual studio 2010 and visual studio 2012 which we use everyday for this project. 
Ignoring too long c++ files is a completely satisfying solution for me. It would be nice for this feature to be reactivated in visual studio 2013. 
Sign in to post a comment.
Posted by gstargate on 3/14/2016 at 4:08 PM
I have run into the same problem using Visual Studio 2013 Version 12.0.21005.1 REL. It says that this issue has been closed. Can you tell me how it was resolved?
Posted by Peter Boräng on 7/7/2014 at 2:19 AM
I just upgraded to VS2013 Update 3 RC and I still get the same crash when intellisense is parsing a large (4.5MB) source file.
Posted by Microsoft on 6/6/2014 at 10:52 PM
Hi Jean-Francois, et. al.,

Thank you to all for your feedback. We have fixed the bug and the changes will be present in our Summer Update CTP for VS 2013. Please verify this when the update comes out and let us know if the issue still persists.

Best regards,
Gabriel Ha
Visual C++ PM
Posted by Peter Boräng on 6/4/2014 at 4:34 AM
This issuesStill exists in VS2013 Update 2.
Posted by M L Boyle on 2/1/2014 at 2:54 PM
I can reproduce this issue (or a similar issue) with VS2013 Update 1. I can provide dumps, etc. Has there been any progress on the bug? Thanks.
Posted by Microsoft on 12/5/2013 at 2:21 AM
Thanks for your feedback.

We are rerouting 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.
Posted by Microsoft on 12/2/2013 at 11:38 PM
Hello again. We wanted to give you a quick reminder that to efficiently investigate and reproduce your issue, we need you to submit the additional information we requested. If we haven't heard back from you with the requested information in the next 3 days, we will go ahead and close the issue.
Posted by Microsoft on 12/1/2013 at 6:14 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 so that we can conduct further research?

Visual Studio has an extension called Microsoft Visual Studio 2013 Feedback Tool, available on the VS gallery(

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 12/1/2013 at 12: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(