Search Issue Tracker
Fixed in 2020.2
Fixed in 2019.3, 2020.1
Votes
1
Found in
2019.3.0a7
2019.3.4f1
Issue ID
1225987
Regression
Yes
Crash on StackAllocator::WalkAllocations when there's a memory leak in Play mode
Reproduction steps:
1. Import the attached .unitypackage to a project ("CrashScene.unitypackage")
2. Open Scene "200%"
3. Enter Play mode
Reproducible with: 2019.3.0a7, 2019.3.6f1
Not reproducible with: 2017.4.38f1, 2018.4.19f1, 2019.3.0a6, 2020.1.0b2, 2020.2.0a3
First lines of the stacktrace:
0x00007FF7773DB8A0 (Unity) StackAllocator::WalkAllocations
0x00007FF7773E8DF6 (Unity) TLSAllocator::WalkAllocations
0x00007FF7773DF60F (Unity) TLSAllocator::FrameMaintenance
0x00007FF7773BF9B0 (Unity) MemoryManager::FrameMaintenance
0x00007FF777CECB64 (Unity) `InitPlayerLoopCallbacks'::`2'::PostLateUpdateMemoryFrameMaintenanceRegistrator::Forward
0x00007FF777CD6388 (Unity) ExecutePlayerLoop
0x00007FF777CD645D (Unity) ExecutePlayerLoop
Note:
- The crash seems to be caused by a memory leak, which in turn when aggressively allocating, often bumps into a SIGSEGV error.
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
- Styling issues in the app toolbar
- Perforce integration - Attempting to add a P4Ignore ignored file does nothing
- URP ScriptableObject SerializeField value set to default during the first Import
- Variables use old overridden values on Prefabs when a variable has FormerlySerializedAs attribute
- [GPU PLM] 100% repro crash when baking EnterTheRoom with 4K maps when using system allocator
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a8
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b7
Resolution Note (fix version 2019.3):
Fixed in 2019.3.11f1