Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.2.6f1
Issue ID
1076527
Regression
No
Unity crashes when inspecting a 'ref return' property when debugging in Visual Studio
Steps to reproduce:
1. Open User-attached project ("RefReturnCrash.zip")
2. Open Scene "Crash"
3. Open Script "Test" and attach the debugger to Unity
4. Create a breakpoint right below the 'Update()' function
5. Play the Scene in Unity
6. Inside VS go to the next step until you reach the 'var write' line
7. Inspect the line by hovering over it and pressing the 'expand' button
Expected: Unity does not crash
Actual: Unity crashes
Reproduced in: 2017.4.10f1, 2018.1.9f2, 2018.2.7f1, 2018.3.0a11
Note: the logs don't seem to provide any useful info or even indicate that the crash happened
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The terrain appears darker when "Per-pixel Normal" is enabled
- [Linux] Editor assertion causes Test Runner to fail when executing it in Batch Mode
- Color selection by the mouse cursor is still enabled when the "Esc" button is pressed
- Game view becomes black and the Scene window becomes grey, “ArgumentOutOfRangeException” errors and “Render Pipeline error” warnings appear after changing the name or deleting URP/HDRP global settings file
- Transform Component is not accessible inside the Player when RuntimeInitializeOnLoadMethod is used
Add comment