Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2017.3.0a1
2018.2.0a1
2018.2.8f1
2018.3.0a1
2019.1.0a1
Issue ID
1092889
Regression
No
Crash on CollectTransformsRecursive when redoing Animator's transform hierarchy optimization
How to reproduce:
1. Open the "Animator_Redo_Crash.zip" project
2. Open the "SampleScene.unity" scene
3. Select "Crash_Model" in the Hierarchy
4. In the Inspector, press Animator settings icon > Optimize Transform Hierarchy
5. Press CTRL-Z
6. Press CTRL-Y
Actual result: Unity crashes.
Reproducible with: 2019.1.0a10, 2019.1.0a1, 2018.3.0b12, 2018.3.0a1, 2018.2.18f1, 2018.2.0a1, 2018.1.9f2, 2017.4.16f1, 2017.3.0a1.
Notes:
In 2017.4 and lower Unity throws "Could not allocate memory: System out of memory!" error.
2019.1.0a1 - 2019.1.0a3 Unity goes into an Infinite loop after pressing "Optimize Transform Hierarchy" and crashes when the computer runs out of memory.
The loop keeps logging error into editor log file:
Setting the parent of a transform which resides in a Prefab instance is not possible.
(Filename: C:/buildslave/unity/build/Runtime/Transform/Transform.cpp Line: 605)
Comments (1)
-
shubhamswaraj2021
Aug 19, 2020 13:26
good one <a href="https://www.lyricsauto.com">lyricsauto</a>
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
- Memory leak when a lot of UI elements are spawned and despawned
- Warnings are not logged in the Console window when using external code analyzers
- Errors “TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations, size 288“ appear constantly when Prefab is open
- Crash on PPtr<Shader>::operator or NullException errors spammed in console when calling Dispose() on null GraphicsBuffer with baked Reflection Probes
- “EndRenderPass: Not inside a Renderpass” and other Render Graph errors in the Player when Render Graph is enabled and Overlay UI is used
Resolution Note:
Will be investigated as part of ongoing undo refactor