Search Issue Tracker

Fixed in 2017.3.0f3

Fixed in 2017.1.X, 2017.2.X

Votes

5

Found in

2017.1.0f3

Issue ID

930062

Regression

No

Unity crashes when debugging using .NET 4.6

Mono

-

Steps to reproduce:
1. Download FarmManagementGame.zip 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

  1. Resolution Note (fix version 2017.3.0f3):

    Fix tested with:
    Visual Studio tools for Unity - 3.9.0.3
    Visual Studio 2017 Version 15.9.4

Comments (24)

  1. Reticulatas

    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.

  2. Reticulatas

    Aug 27, 2017 00:38

    FIXED

    Updating to Visual Studio 15.4 preview build resolves this issue.

  3. Reticulatas

    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.

  4. Reticulatas

    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: https://issuetracker.unity3d.com/issues/unity-crashes-when-debugging-with-vs2017-when-using-net-4-dot-6

Add comment

Log in to post comment

All about bugs

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