VS2015 crashes every time I update npm package version

[alanpurple]

windows 10 pro x64
vs 2015 enterprice
nodejstool 1.1 rc
iojs 3.0.0
python 2.7.10 x64
node-gyp in iojs 3.0.0 is intalled globally

stop working -> restarting

[mousetraps]

Thx for reporting this. Since VS crashed, there should be a corresponding entry (or entries) in the windows event log. Mind grabbing that for us?

Also can you be a little more specific about how you're updating the package version? Are you using the context menu command, or something else?

[alanpurple]

@mousetraps where is log? I can't find it in C:\user\username\AppData\Roaming\Microsoft\VisualStudio\14.0

package doesn't matter I think, this time mongoose 4.1.1 -> 4.1.2, I usually just modify package.json and save and then addon run script automatically

anyway package was updated successfully after these crash and restart

[mousetraps]

Control Panel > System and Security > Administrative Tools > Event Viewer

[billti]

Or just use the "Windows Key + X" (the handiest but least known Windows shortcut) to open the menu, and then press "V" (for Event Viewer).

p.s. "Win + X, A" is another super handy combo I use all the time for an Admin prompt.

[billti]

p.s. The log to look at will be under 'Windows Logs / Application'. Most app crashes get an event in here.

[alanpurple]

@mousetraps 2 errors occured one other right after one

1. Event 1026, .NET runtime
   Application: devenv.exe
   Framework Version: v4.0.30319
   Description: The process was terminated due to an unhandled exception.
   Exception Info: System.IO.PathTooLongException
   Stack:
   at System.IO.Path.NormalizePath(System.String, Boolean, Int32, Boolean)
   at System.IO.Path.GetDirectoryName(System.String)
   at Microsoft.VisualStudio.Services.DirectoryWatcher+d__132.MoveNext()
   at System.Linq.Enumerable+d__11[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext() at System.Linq.Enumerable.Contains[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Collections.Generic.IEnumerable1<System.__Canon>, System.__Canon, System.Collections.Generic.IEqualityComparer1<System.__Canon>) at System.Linq.Enumerable.Contains[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Collections.Generic.IEnumerable1<System.__Canon>, System.__Canon)
   at Microsoft.VisualStudio.Services.DirectoryWatcher.ProcessDirectoryChanges(System.Collections.Generic.IEnumerable1<System.Collections.Generic.KeyValuePair2<System.String,Microsoft.VisualStudio.Services.ChangeStreamDigest>>, Int32)
   at Microsoft.VisualStudio.Services.DirectoryWatcher.ProcessChanges(System.Collections.Generic.IEnumerable1<System.Collections.Generic.KeyValuePair2<System.String,Microsoft.VisualStudio.Services.ChangeStreamDigest>>, Int32)
   at Microsoft.VisualStudio.Services.DirectoryWatcher.ProcessChanges(System.Collections.Generic.IEnumerable1<System.Collections.Generic.KeyValuePair2<System.String,Microsoft.VisualStudio.Services.ChangeStreamDigest>>, Int32)
   at Microsoft.VisualStudio.Services.DirectoryWatcher.OnChangedAsync()
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.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 System.Windows.Threading.ExceptionWrapper.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)
2. Event 1000, Application Error
   Faulting application name: devenv.exe, version: 14.0.23107.0, time stamp: 0x559b7ead
   Faulting module name: KERNELBASE.dll, version: 10.0.10240.16384, time stamp: 0x559f3b2a
   Exception code: 0xe0434352
   Fault offset: 0x000b3e28
   Faulting process id: 0x2114
   Faulting application start time: 0x01d0d440e6db3ccb
   Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe
   Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
   Report Id: 749ac6f7-d457-4dbb-922c-a4dfc2ab5c9e
   Faulting package full name:
   Faulting package-relative application ID:

looks like this is caused by "Too long path" related. similar to warning when I first try to build my node.js project.

[billti]

This is an unfortunately limitation of .NET that impacts some Node projects due to the way node modules nest in the file system (see http://blogs.msdn.com/b/bclteam/archive/2007/02/13/long-paths-in-net-part-1-of-3-kim-hamilton.aspx ).

As a potential workaround, is the project stored at an already lengthy path (e.g. "C:\users\some name\documents\visual studio 2015...")? If so, can you try moving the project to somewhere like "C:\src" and seeing if the problem persists?

[billti]

(note: that doesn't change the fact this shouldn't crash and we need to handle this exception better - and give useful guidance when caught - but hopefully that will unblock you)

[mousetraps]

I think this might actually be coming from web tools, not from ntvs - he mentioned that the script is run immediately after he saves.

[alanpurple]

@billti my project is like F:\VSWorkspace\project1\src\project1, not that long I think

@mousetraps It's not web tool, I didn't use any tool other than VS2015 itself and ntvs

[alanpurple]

@billti I think express plugins' dependency hierarchy is usually bit deep, maybe that's reason how the path is so long