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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
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