Search Issue Tracker
By Design
Votes
0
Found in
2020.3
2020.3.22f1
2021.2
2022.1
2022.2
Issue ID
1382261
Regression
No
[Serialization] Player build hangs on initial loading screen after reporting UnloadTime in the Player log
Reproduction steps:
1. Open the attached user's project "boardgame_demo.zip"
2. Open the "Assets\Scenes\BoardTest.unity" Scene
3. Build for Standalone
Expected result: Player does not hang and memory usage does not increase gradually leading to a crash
Actual result: Player hangs and memory usage increases gradually leading to a crash
Reproduces on: 2020.3.27f1, 2021.2.9f1, 2022.1.0b5, 2022.2.0a4
Could not test on 2019.4.36f1 due to console errors when downgrading
Notes:
-Issue reproduces with IL2CPP and Mono backends
-Issue also reproduces on WebGL
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
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
Resolution Note (2022.2.X):
This issue is caused by an infinite loop in your project caused by Board::Awake invoking HardDespawn, The player path for this is invoking Destroy which will not invoke the destruction of the object directly while the looping code is assuming that it does leading to an infinite loop. If you replace it with DestroyImmediate it will not loop infinitely but this is still not the best pattern for the cleanup intended it would be better to start from a clean initial state rather than doing it there.