VS 2012.2 crashes when viewing any aspx file - by MicahA

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 785630 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 4/25/2013 6:35:19 PM
Access Restriction Public


Faulting application name: devenv.exe, version: 11.0.50727.1, time stamp: 0x5011ecaa
Faulting module name: msenv.dll, version: 11.0.50727.1, time stamp: 0x5011ecbd
Exception code: 0xc0000005
Fault offset: 0x000a292a
Faulting process id: 0x163c
Faulting application start time: 0x01ce42105e8a8448
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe
Faulting module path: C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\msenv.dll
Report Id: c81ce0fb-ae03-11e2-a5ba-20689d676536

Exception Info: System.AccessViolationException
   at Microsoft.VisualStudio.TextManager.Interop.IVsExpansionManager.EnumerateExpansions(System.Guid, Int32, System.String[], Int32, Int32, Int32, Microsoft.VisualStudio.TextManager.Interop.IVsExpansionEnumeration ByRef)
   at Microsoft.VisualStudio.Web.Snippets.SnippetListManager+SnippetCache.CacheLanguageExpansionStructs(Microsoft.VisualStudio.TextManager.Interop.IVsExpansionManager, System.Guid)
   at Microsoft.VisualStudio.Web.Snippets.SnippetListManager+SnippetCache..ctor(Microsoft.VisualStudio.TextManager.Interop.IVsExpansionManager, System.Guid, SnippetCache)
   at Microsoft.VisualStudio.Web.Snippets.SnippetListManager.ResetSnippetCache(System.Guid)
   at Microsoft.VisualStudio.Web.Snippets.SnippetListManager.EnsureInitialized(System.Guid)
   at Microsoft.VisualStudio.Web.Snippets.SnippetListManager.GetInstance(System.Guid)
   at Microsoft.VisualStudio.Web.Factory.Microsoft.VisualStudio.Web.Interop.IMVWFactory.CreateSnippetListManager(System.Guid)
   at Microsoft.VisualStudio.Shell.Interop.IOleInPlaceComponent.FDoIdle(UInt32)
   at Microsoft.VisualStudio.Platform.WindowManagement.OleInPlaceComponentIdleManager.PassOnIdleTime(System.Collections.Generic.List`1<Microsoft.VisualStudio.Shell.Interop.IOleInPlaceComponent>, Microsoft.VisualStudio.PlatformUI.OleComponentSupport.IdleTypes)
   at Microsoft.VisualStudio.Platform.WindowManagement.OleInPlaceComponentIdleManager.FDoIdleCore(UInt32)
   at Microsoft.VisualStudio.PlatformUI.OleComponentSupport.OleComponent.Microsoft.VisualStudio.OLE.Interop.IOleComponent.FDoIdle(UInt32)
Sign in to post a comment.
Posted by Microsoft on 5/9/2013 at 11:35 AM
Thank you for passing along this issue to us. At this point, we are pulling together this and other feedback as part of our planning and evaluation for the next release. We know that our customers are the most qualified people to help us learn how to make our products better, and we greatly appreciate hearing from you.
Posted by Microsoft on 4/29/2013 at 12:09 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 4/26/2013 at 2:10 AM
Thanks for your feedback. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.
It may help if you provide us with Bucket ID, a dump file and call stack.

Bucket ID:
1.    Open Event Viewer        
2.    Click on Windows Logs -> Application
3.    Search for a 1001 event that occurred soon after you encountered the crash
4.    The bucket ID should be available in the event details
(there may be multiple 1001 events for any given crash - only one will have the bucket ID)
Dump File and Callstack:
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 zip the file and use "FeedbackID-785630" as prefix of the file name.

You can use the following workspace to upload the file:
Password is WEXBO$l0qc66vw9b

Thanks again for your efforts and we look forward to hearing from you.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 4/25/2013 at 6:51 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)