Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 2017.1.X, 2017.2.X
Votes
12
Found in
2017.1.0f1
Issue ID
926881
Regression
No
Editor crashes when examinating values in debugger with .NET 4.6
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.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader Compilation for projects with lots of Shaders can be slow (i.e. VFX Graph asset heavy projects)
- The Editor hangs when opening a project that uses local packages and Version Control
- Area Light is culled when Camera Frustrum is outside the lights range
- The characters of the bottom option in the Scene View Debug Draw Mode dropdown menu are cut off
- Graph and Camera options for Render Graph Viewer disappear after maximising the window
theinfo22
Aug 12, 2020 19:26
nice you can ask here https://trailblazers.salesforce.com/answers?id=90630000000gpOtAAI
cozyurt_unity
Jul 17, 2020 14:02
kedi maması köpek maması www.patilimama.com
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.
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.
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.
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.
Baste
Aug 21, 2017 13:16
This is happening pretty frequently for me!
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.