Search Issue Tracker
Active
Fixed in 2023.1.18f1, 2023.2.0b15, 2023.3.0a5
Under Consideration for 2022.3.X
Votes
1
Found in
2022.3.5f1
2023.1.4f1
2023.2.0a23
2023.3.0a1
Issue ID
UUM-43709
Regression
No
High memory usage and crash on DynamicHeapAllocator::CreateTLSFBlock when opening project with Sprite Atlas V2 enabled
Reproduction steps:
1. Open the attached project “CrashRepro“
2. Observe memory usage
Expected result: Memory usage is normal
Actual result: Almost all of the memory gets used up at some point and can crash
Reproducible with: 2021.2.0b1, 2022.1.0a1, 2022.1.24f1, 2022.3.5f1, 2023.1.4f1, 2023.2.0a23
Not reproducible with: 2021.3.28f1
Reproducible on: Windows 10
Note: The crash is very inconsistent, but memory consumption always increases about halfway through the project loading
First few lines of stack trace:
{noformat}[00] DynamicHeapAllocator::CreateTLSFBlock
[01] DynamicHeapAllocator::Allocate
[02] DualThreadAllocator<DynamicHeapAllocator>::Allocate
[03] MemoryManager::Allocate
[04] malloc{noformat}
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
- Crash on AudioUtil_CUSTOM_HasAudioCallback when entering PlayMode while the GameObject's Properties Inspector window is in Debug mode
- Tilemap Collider 2D is not updating the Collider shapes when removing Tiles on the Tilemap component
- Inspector with the scrollbar is unusable when Material properties are edited and the scene is saved
- The Rendering Profiler module statistics are zero when Application.targetFrameRate is set
- The Editor becomes unresponsive and memory allocation errors are spammed in the Console when Generating Lightning
Resolution Note (fix version 2023.3.0a5):
Fix for this issue will be available on Unity 2023.3.0a5 and above
Resolution Note (fix version 2023.2.0b15):
Fix for this issue is available on Unity 2023.2.0b15 and above
Resolution Note (fix version 2023.1.18f1):
Fix for this issue is available on Unity 2023.1.18f1 and above