Search Issue Tracker

Fixed in 2017.3.0f3

Fixed in 2017.1, 2017.2

Votes

12

Found in

2017.1.0f1

Issue ID

926881

Regression

No

Editor crashes when examinating values in debugger with .NET 4.6

Mono

-

Usual reproduction steps:
1. Open a specific project in .NET 4.6.
2. Enter play mode or recompile scripts.
Result: Sometimes editor crashes (very low chance).

Stable reproduction steps (might be another problem but similar stacktrace):
1. Open project (ReflectionTest.zip)
2. Open scene "Root"
3. Open script "Reflection"
4. put a breakpoint on line 20
5. Stepped to the next line
6. Try to examine info base values. (info/base/base and it crashes).
Result: Editor crashes steadily.

Reproduced on: .NET 4.6.
Works fine with .NET 3.5.

Comments (6)

  1. Ff74989fb6d1bfdddb3a0db308eea425?d=mm

    HeavensSword

    Sep 04, 2017 16:08

    This occurred very frequently for me. I'm not 100% sure, but after recompiling code in vs2017 and shifting back to unity, there is a momentary hitch when I believe unity is refreshing/reimporting. If I hit play before it does that or I have visual studio attached for debug, I think my chances of a crash sky rocket. Again, could just be coincidence.

  2. 1c1be0cc35d1a5cbbbb7a5825dda65df?d=mm

    Mariusj

    Sep 04, 2017 14:09

    This issue will be fixed in future releases. Anyway, there might some other problems that might cause a crash with .NET 4.6. We have not fixed them all yet so if anyone encounters a crash, then make sure to report them with Bug Reporter and add reproduction steps if possible.

  3. 537d2a1daafc314e65c50a1ee9ea6e4a?d=mm

    ksakins

    Aug 29, 2017 11:58

    Same here, it's happening pretty frequently since updating to VS2017 and Unity 2017. However around the same time I switched to start using .NET 4.6 in my Unity Project -- so it's hard for me to tell which change is the cause of the issue.

  4. 2a4f6aecd17bc81ffe95489fce049d7d?d=mm

    EvansT

    Aug 23, 2017 01:25

    This happens quite frequently for me - Sometimes once every 15 minutes. Attaching the Visual Studio debugger might be making the issue worse, I guess.

  5. Ba1baa3f0bad1e109a59bfb6a609ba33?d=mm

    Baste

    Aug 21, 2017 13:16

    This is happening pretty frequently for me!

  6. 672d1dd2e4aac99b5a0983b7eaf7f3aa?d=mm

    Sloane

    Aug 16, 2017 11:04

    I don't have anything helpful to add except it's not a very low chance, about 25% on two different projects I've been working on.

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.