Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
0
Found in
2022.3.74f1
6000.0.70f1
6000.3.11f1
6000.4.0b12
6000.5.0a8
6000.6.0a1
Issue ID
UUM-136691
Regression
No
Crash on DualThreadAllocator<DynamicHeapAllocator>::Allocate when entering Play mode on a specific scene
How to reproduce:
1. Open the attached “IN-135307” project
2. Open the “PullShot” scene
3. Enter Play mode
4. Wait for ~1 minute
5. Observe the crash
Reproducible with: 2022.3.7f1, 2022.3.74f1, 6000.0.70f1, 6000.3.11f1, 6000.4.0b12, 6000.5.0a8
Could not test with: 2022.3.6f1 (could not solve errors from downgrading)
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
- Sometimes the crash occurs when exiting play mode
- The crash does not occur after commenting out void FixedUpdate() in PullAgentRange.cs
First few lines of the stack trace:
0x00007ff6d2cc70ee (Unity) DualThreadAllocator<DynamicHeapAllocator>::Allocate
0x00007ff6d2cb8d01 (Unity) MemoryManager::Allocate
0x00007ff6d2cc31ae (Unity) malloc_internal
0x00007ff6d2fe47f6 (Unity) DebugDidScheduleJob
0x00007ff6d2fed2e4 (Unity) JobBatchDispatcher::ScheduleMultiDependencyJob
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
Add comment