Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.2.X, 2021.1.X
Votes
0
Found in
2020.1.0a18
2020.1.14f1
2020.2
2021.1
Issue ID
1297307
Regression
Yes
Crash on StackAllocator::WalkAllocations when loading another Scene whilst in Play Mode
How to reproduce:
1. Open the project attached "1297307.zip"
2. Open any Scene
3. Enter Play Mode
4. Double click other Scene (might take a few tries for repro)
Reproducible with: 2020.1.0a18, 2020.1.17f1, 2020.2.0b14, 2021.1.0a9
Does not reproduce with: 2018.4.30f1, 2019.4.16f1, 2020.1.0a17
Notes:
1. Reproduces on 2020.1.17f1 2/3 times.
2. On older versions than 2020.1.17f1 reproduces very inconsistently (about 1/7 times), stopped reproducing entirely on 2020.1.0a17.
3. Probably an issue with Project Settings, as deleting the folder fixes the issue but manually resetting each Project Setting tab does not.
First lines of stacktrace:
0x00007ff6ec129636 (Unity) TLSAllocator::WalkAllocations
0x00007ff6ec1279a1 (Unity) TLSAllocator::FrameMaintenance
0x00007ff6ec11e2c0 (Unity) MemoryManager::FrameMaintenance
0x00007ff6ec46588b (Unity) `InitPlayerLoopCallbacks'::`2'::PostLateUpdateMemoryFrameMaintenanceRegistrator::Forward
0x00007ff6ec44d38c (Unity) ExecutePlayerLoop
0x00007ff6ec44d463 (Unity) ExecutePlayerLoop
0x00007ff6ec4541e9 (Unity) PlayerLoop
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
- INVALID_ENUM warning is thrown in WebGL Player when building an empty scene
- Crash on ApiGLES::ClearBufferSubData when running the Player a second time on Meta Quest 2
- "Process VFXCamera Command" column is displayed in the "Render Graph Viewer" when there are no VFX in the Scene
- [Performance] Vulkan performing much worse than OpenGLES due to excessive buffer copies on Quest 2/3
- An error 'AssertionException: Assertion failure. Value was False' is displayed in the Console when maximizing or unmaximizing the UI Builder
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a3
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0b4
Resolution Note (fix version 2020.2):
Fixed in 2020.2.4f1