Search Issue Tracker
Third Party Issue
Votes
0
Found in
6000.0.38f1
6000.1.0b6
6000.2.0a3
Issue ID
UUM-97531
Regression
No
Crash on mono_get_hazardous_pointer when running Play Mode tests in a specific project
How to reproduce:
1. Open the attached “IN-93288_Crash_Repro.zip“ project
2. Open the Test Runner window (Window>General>Test Runner)
3. In the window, select “Play Mode“
4. Press “Run All“ button at the bottom right of the window
Reproducible with: 6000.0.38f1, 6000.1.0b6, 6000.2.0a3
Couldn’t test with: 2022.3.58f1 (Errors in the Console)
Reproducible on: macOS 14.6.1 Sonoma (Intel), Windows 11 (by user)
Not reproducible on: No other environment tested
First few lines of the stack trace:
#0 0x00000181ad0f10 in mono_get_hazardous_pointer
#1 0x00000181a28a9e in mono_jit_info_table_find_internal
#2 0x00000181925e52 in mini_jit_info_table_find_ext
#3 0x000001819250b6 in mono_summarize_unmanaged_stack
#4 0x00000181a7cbe3 in mono_threads_summarize_native_self
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
After investigation we have determined that the crash is coming from a third party entity library that is accessing invalid memory.