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
- SystemInfo.get_graphicsDeviceName() is generating garbage GC Alloc when using Metal graphics API
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
Add comment