1

Closed

Intellisense crash

description

After installation, VS 2013 crashes when JavaScript intellisense is active. Able to build and deploy applications except for crashing of intellisense.
Closed May 20 at 3:59 PM by Zooba
Caused by WebEssentials requiring VSU2

comments

RajKrishnan wrote Mar 28 at 4:14 PM

When I uninstall the tool, everything works fine. So something in the tool is messing up VS 2013 intellisense.

Zooba wrote Mar 28 at 4:55 PM

If you look in your Event Viewer under the Application Log, you should see some error entries (they'll be labelled "Application Error" and ".NET Runtime"). If you can share the details of these errors, that will help us greatly.

kgu87 wrote May 12 at 10:29 AM

Below is the error trace on this. Behavior - IDE crash when clicking on a .JS file inside python (flask) project.

Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
Stack:
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__0(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

kgu87 wrote May 12 at 10:42 AM

More info -

The crash goes away when WebEssentials package is removed from VS 2013.

Zooba wrote May 19 at 6:08 PM

It is possible that you've updated to the latest WebEssentials but haven't installed VS 2013 Update 2? I get a very similar looking crash from WebEssentials that seems to be unrelated to PTVS.

kgu87 wrote May 19 at 7:42 PM

It appears that this is exactly what it was. Thanks!