Search Issue Tracker
Fixed
Fixed in 6000.0.59f1, 6000.2.2f1, 6000.3.0a4
Votes
20
Found in
2021.3.47f1
2022.3.56f1
6000.0.35f1
6000.1.0b2
6000.2.0a1
6000.3.0a1
Issue ID
UUM-92619
Regression
No
Crash on CleanupAfterLoad() when exiting Play Mode during Async Scene load/unload events
How to reproduce:
1. Open the “CrashRepro“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Enter Play Mode
4. Wait 20 seconds
5. Exit Play Mode
Reproducible with: 2021.3.47f1, 2022.3.56f1, 6000.0.35f1, 6000.1.0b2
Reproducible on: macOS 15.2 Sequoai (Intel), Windows 10 (reported by user)
Not reproducible on: No other environment tested
Note: If issue is not reproduced first time, steps 3 - 5 need to be repeated
First few lines of stack trace:
#0 0x00000000000001 in (Unknown)
#1 0x0000010ceb9705 in CleanupAfterLoad()
#2 0x0000010cf28b94 in LoadSceneOperation::CompletePreloadManagerLoadSceneEditor()
#3 0x0000010cf28301 in LoadSceneOperation::IntegrateMainThread()
#4 0x0000010cf2b0d1 in PreloadManager::UpdatePreloadingSingleStep(PreloadManager::UpdatePreloadingFlags, int)
Comments (2)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
stonstad
Aug 13, 2025 16:08
Associated Unity discussion: https://discussions.unity.com/t/unity-built-in-physics-crash-crash-and-more-crashing/1650018/6
stonstad
Aug 11, 2025 19:24
This fix has been in review for almost two months. Is there an update to this issue? I'm using what is supposed to be a stable version of Unity (6.0), but it's far from it with the sheer volume of crashes caused by this issue.
Unity, please get this across the finish line.