Search Issue Tracker
Not Reproducible
Not Reproducible in 6000.3.X
Votes
0
Found in
6000.3.0f1
Issue ID
UUM-132895
Regression
No
Crash on Transform::RebuildTransformHierarchy when saving Scene after exiting the Play Mode
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/EngravingAnimation.unity” Scene
3. Enter the Play Mode
4. Open any Script file
5. Made some changes in the file and save it (ctrl+s)
6. Exit the Play Mode
7. Save the Scene (ctrl+s)
6. Observe the Crash
Reproducible with: 6000.3.4f1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note: Not reproduced by CQA
First few lines of the stack trace:
{{0x00007FF8A5EEE713 (Unity) Transform::RebuildTransformHierarchy }}
{{0x00007FF8A6CBD61A (Unity) SynchronizeMeshRenderersAndMaterials }}
{{0x00007FF8A6CBD54A (Unity) AssetHotreload }}
{{0x00007FF8A7C1A0E2 (Unity) AssetHotreload}}
{{0x00007FF8A7C8E673 (Unity) HotreloadV2 }}
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.
Resolution Note (6000.3.X):
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.