Search Issue Tracker
Fixed in 2017.1.0f3
Fixed in 5.3.X, 5.4.X, 5.5.X, 5.6.X, 2017.1.X
Votes
4
Found in
5.6.0f3
2017.1.0b1
Issue ID
898809
Regression
Yes
Crash in UI::CalculateNestedAlpha when Game Object is given different parent
Editor crashes when CanvasGroup's alpha value is changed and the game object is then given a different parent in the hierarchy by Transform::SetParent.
To reproduce:
1. Open the attached project
2. Open "CrashTest" scene
3. Select "RootCanvas" -> "crash_test_bar" game object from the hierarchy
4. Right click "CrashTest" component and click "crash" item on context menu
Desired outcome: The "crash_test_bar" object is deactivated and becomes a child of "OtherNode" game object in the hierarchy.
Actual result: Editor crashes.
Reproduced with 5.5.2p4, 5.5.3p1, 5.6.0f2, 5.6.0f3, 2017.1.0b1
Not reproduced with 5.5.2p2, 5.5.2p3, 5.6.0f1, 2017.1.0a6
Regression introduced in 5.5.2p4, 5.6.0f2, 2017.1.0b1
Backported to: 5.4.5p3, 5.5.3p4, 5.6.1p1, 2017.1.0b9
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
- [iOS] Back Triple Camera is not focusing manually and automatically
- Mouse inputs cannot be inputted when searching the Shortcuts Menu by type "Shortcut"
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
andymilsom
May 11, 2017 11:17
If you are affected by this issue and use SetActive(false) before the call to SetParent. A known workaround to the issue is to delay the call to SetActive(false) to after SetParent.
samizzo
Apr 16, 2017 14:19
I'm seeing this in 5.6.0f3 as well.