ArgumentNullException (and possibly others) hard crash the debugger (and the application)

[JHorvath-MaxetaTech]

Environment data

.NET Command Line Tools (2.1.200)

Product Information:
Version: 2.1.200
Commit SHA-1 hash: 2edba8d7f1

Runtime Environment:
OS Name: Windows
OS Version: 10.0.17134
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\2.1.200\

Microsoft .NET Core Shared Framework Host

Version : 2.0.7
Build : 2d61d0b043915bc948ebf98836fefe9ba942be11

VS Code version: 1.23.1

C# Extension version: 1.15.1

Steps to reproduce

1. dotnet new webapi

2. update ValuesController with the following get

    // GET api/values/5
    [HttpGet("{id}")]
    public string Get(int id) {
      String result = null;
      switch (id) {
        case 1:
          throw new Exception("One");
        break;
        case 2:
          throw new ArgumentNullException("Two");
        break;    
        case 3:
          String template = null;
          result = String.Format(template, "Three");
        break;
      }
      return result;
    }

3. Start the project in VSCode (F5 - With debugging)

4. Browse to http://localhost:5000/api/values/1
   Debugger will catch exception and continuing will return the Developer Exception Page to the browser

5. Browse to http://localhost:5000/api/values/2
   Debugger will hard crash the application

6. Start the project in VSCode (CTRL+F5 Without Debugging)

7. Browse to http://localhost:5000/api/values/2
   The Developer Exception Page is returned to the browser

Expected behavior

When encountering an ArgumentNullException the debugger should break on the offending line, display appropriate information, and allow for continued execution.

Actual behavior

The debugging session hard crashes along with the application.

[JHorvath-MaxetaTech]

P.S. This appears to affect newer debugger versions, I had another developer with an older version test (sorry don't have the specific version number), and it worked as expected, but upon upgrading to the latest version 1.15.1, he encountered the same issue I did.

[gregg-miskelly]

@JHorvath-MaxetaTech Thanks for reporting this! We should have a fix out very soon.