Crash on DynamicHeapAllocator::CreateTLSFBlock when opening a scene with specific GameObjects

Unity: Scene Management

Won't Fix

6.6.X

6.5.X

6.4.X

6.3.X

6.0.X

2022.3.X

Thank you for reporting a bug to Unity. We have reviewed the issue carefully, and in this case, the team won't fix the issue. The SolarSystemScene.unity file is broken beyond repair, objects have bad IDs, there multiple instances of what is supposed to be singletons and so on. The scene seems to have been in a bad merge or somehow auto generated, it was definitely not serialized by the Unity editor.

How to reproduce:
1. Open the attached “IN-136296” project
2. Open the “SolarSystemScene“ (Assets > Scenes)
3. Observe the crash

Reproducible with: 2022.1.22f1, 2022.3.74f1, 6000.0.70f1, 6000.3.11f1, 6000.4.0b12, 6000.5.0a9

Reproduced on: Windows 11
Not reproduced on: No other environment tested

Note: Most of the time, the scene will load infinitely instead of crashing

First few lines of the stack trace:
0x00007FF6FDC8E100 (Unity) DynamicHeapAllocator::CreateTLSFBlock
0x00007FF6FDC8CBD8 (Unity) DynamicHeapAllocator::Allocate
0x00007FF6FDC9B74C (Unity) DualThreadAllocator<DynamicHeapAllocator>::Allocate
0x00007FF6FDC8D2F1 (Unity) MemoryManager::Allocate
0x00007FF6FDC9779E (Unity) malloc_internal

Crash on DynamicHeapAllocator::CreateTLSFBlock when opening a scene with specific GameObjects

Unity: Scene Management

Won't Fix

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Crash on DynamicHeapAllocator::CreateTLSFBlock when opening a scene with specific GameObjects

Unity: Scene Management

Statuses

Won't Fix

Resolution Notes

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?