Search Issue Tracker

Fixed in Unity 2017.3



Found in


Issue ID




Unity crashes when debugging using .NET 4.6




Priority: 3Not yet prioritized for a release


Severity: 1Crash or major loss of functionality

Steps to reproduce:
1. Download project and open
2. Set up a breakpoint in GrowingState.cs at line 30
3. Attach to Unity and press play
4. Press one of the white squares wait a bit and repeat this step two more times
5. When breakpoint triggers step into it

Results: editor crashes when stepping into line 31. Doesn't reproduce when using .NET 3.5

Note: .NET 4.6 was introduced in 2017.1, 2017.2

Reproduced with: 2017.3.0a7 2017.2.0b2, 2017.1.0f3

Comments (5)

  1. 5784d38be885d6bf6a94aab1103bd136?d=mm


    Nov 08, 2017 20:45

    Unity still crashes with VS - version 15.4.3. I can step through a few lines of code, then unity and vs stop working.

  2. D7b6d49aa47ef08160acb15ed367d776?d=mm


    Aug 27, 2017 01:35

    EDIT 15.4 preview build only partly resolves the issue, I can see that the debugger attaches properly and will break in some code. However, the instant I call into an external library, Unity crashes.

  3. D7b6d49aa47ef08160acb15ed367d776?d=mm


    Aug 27, 2017 00:38


    Updating to Visual Studio 15.4 preview build resolves this issue.

  4. D7b6d49aa47ef08160acb15ed367d776?d=mm


    Aug 22, 2017 01:03

    Attempted to use VS2015 with VS tools for unity. Attempted steps:

    1) Attach to Unity
    2) Set breakpoint
    3) Run game
    Result: Breakpoint is never hit

    1) Attach to Unity
    2) Run game
    3) Set breakpoint
    Result: Unity Editor crashes when breakpoint is hit.

    So it seems to matter when you put the breakpoint.

  5. D7b6d49aa47ef08160acb15ed367d776?d=mm


    Aug 21, 2017 15:03

    I have this as well. 100% consistent silent unity crash when using VS2017 and hitting a breakpoint.

    There is a dupe of this here:

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.