Search Issue Tracker
Active
Under Consideration for 6000.3.X
Votes
0
Found in
6000.3.2f1
Issue ID
UUM-131529
Regression
No
Crash with multiple stack traces when completing various actions with the Visual Studios IDE
A crash in the Editor has been reported, affecting various workflows. These workflows include:
- Entering Play mode
- Detaching or attaching the debugger
- Reloading the code domain
Reproducible with: 6000.3.2f1
Reproduced on: Windows 11 (users machine)
Not reproduced on: No other environment tested
Notes:
- Not reproduced by CQA after testing on Windows 11
- The issue occurs regardless of whether the debugger is attached or not
- It is undetermined whether this occurs with different IDEs
First few lines of the stack trace:
0x00007FFFAC4CF095 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\metadata.c:6160] do_mono_metadata_type_equal
0x00007FFFAC4F584C (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\mono-hash.c:122] mono_g_hash_table_find_slot
0x00007FFFAC56AF03 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\reflection.c:491] mono_type_get_object_checked
0x00007FFFAC506B0E (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\object.c:2282] mono_class_create_runtime_vtable
or:
0x00007FFF8F94CB02 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\mini\debugger-engine.c:386] collect_domain_bp
0x00007FFF8F94D2F1 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\mini\debugger-engine.c:454] mono_de_set_breakpoint
0x00007FFF8F941BA3 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\mini\debugger-agent.c:7654] event_commands
0x00007FFF8F94A9C6 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\mini\debugger-agent.c:10445] debugger_thread
or:
0x00007FFEEE74782A (KERNELBASE) RaiseException
0x00007FFD05DF120C (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\utils\mono-log-common.c:143] mono_log_write_logfile
0x00007FFD05DDCE12 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\eglib\goutput.c:172] monoeg_g_logv_nofree
0x00007FFD05DDCE78 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\eglib\goutput.c:187] monoeg_g_log
or:
0x00007FFA8DA4E7D1 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\metadata.c:6064] mono_metadata_class_equal
0x00007FFA8DA4F132 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\metadata.c:6197] do_mono_metadata_type_equal
0x00007FFA8DA7584C (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\mono-hash.c:122] mono_g_hash_table_find_slot
0x00007FFA8DAEAF03 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\reflection.c:491] mono_type_get_object_checked
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment