Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.3.X
Votes
0
Found in
2018.4
2019.2.17f1
2020.1
Issue ID
1210416
Regression
No
Crash on inspecting Dictionary contents, which include an enum, when debugging in Visual Studio
Steps to reproduce:
1. Open the attached project
2. Open "SampleScene" Scene
3. Open the "test.cs" script in Visual Studio and set a breakpoint inside Update method
4. Attach the VS debugger to Unity
5. Enter Play mode
6. Attempt to inspect testDictionary contents
Reproducible with: 2018.4.16f1, 2019.2.20f1, 2019.3.0f6, 2020.1.0a21
Couldn't test with: 2017.4 since Visual Studio Unity debugging is not available in this stream
Last line in the Editor log before the crash (not always produced):
* Assertion: should not be reached at ..\mono\mini\debugger-agent.c:7753
Notes:
- From the crash dumps it seems that the crash comes from abort.cpp which is a Windows file
- The crash doesn't reproduce when inspecting a List which contains the same enum
- The crash does reproduce independently of if the enum is used as a value or a key
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note (fix version 2020.1):
Managed debugger didn't handle the case where we are inspecting a generic struct and the field is an enumerator. This has been fixed in 2020.1.0a24
Resolution Note (fix version 2019.3):
Fixed in 2019.3.7f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.24f1