Unhandled exception crashes VS2013

Jul 28, 2014 at 11:34 AM
While testing latest NTVS version my vS2013 regularly crashes. It happens just before breakpoint should be hit. In beta 1 I got this crash also, even more regularly, but there was other error logged. I’m using typescript project. Dump from my application events is:

Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Collections.Generic.KeyNotFoundException
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__5(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(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.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()


Faulting application name: devenv.exe, version: 12.0.30501.0, time stamp: 0x5361f453
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17055, time stamp: 0x532943a3
Exception code: 0xe0434352
Fault offset: 0x00011d4d
Faulting process id: 0x1448
Faulting application start time: 0x01cfaa55e0418b61
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: 0d3a9720-164a-11e4-8262-c4d9878cc84a
Faulting package full name:
Faulting package-relative application ID:
Aug 3, 2014 at 8:36 PM
Same here, with the same log. It happens, when you remove a breakpoint before should be hit (set two breakpoints, remove second on debug).
Aug 4, 2014 at 6:10 AM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Marked as answer by RickWinter on 8/4/2014 at 10:06 AM
Aug 22, 2014 at 5:23 PM
I seem to be unable to reproduce this on the most recent dev build. Can you share the code snippet on which this happens for you?
Aug 25, 2014 at 7:12 AM
Edited Aug 25, 2014 at 12:32 PM
@pminaev, it is very easy to reproduce, just follow these steps (I use latest dev build, Aug 13, 2014):

Create new node ts console project and in the app.ts add following code:
import _lib = require("./lib");
Add new typescript file lib.ts:
export function foo() {
    console.log("Line 1");
    console.log("Line 2");
    console.log("Line 3");
Now set two breakpoints in lib.ts, one on “Line 1” and second on “Line 2”. Start debugging, debugger should stop on “Line 1” and breakpoint in “Line 2” will be like unavailable. (The breakpoint will not currently be hit… ). Now remove second breakpoint and press F5 and VS will crash.

Best regards

let me know if you need more info
Aug 25, 2014 at 6:08 PM
A perfect repro, thank you! Looking into it now.