Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.5.0b2
Issue ID
831520
Regression
No
Canvas Group component is still active even when it is manually disabled in the Inspector
Canvas Group component is still calling "RandomSibling.Update()" even when "Canvas group" is disabled in the inspector.
Steps to reproduce:
1. Open attached project
2. Open "CanvasGroupMakesSetSiblingIndexReallySlow"
3. Select GameObject->Canvas
4. Go into play mode
5. Open Deep Profile and select BehaviourUpdate->RandomSibling.Update() (it should be using no more that 20% of CPU)
6. Now press Add Component->Canvas group (watch attached video)
7. RandomSibling.Update() increases to >90% in deep profiler
8. Now disable Canvas Group component in the Inspector
-RandomSibling.Update() still running >90%
Actual result: "Canvas Group" is still active even when it is disabled in the inspector.
Expected result: "Canvas Group" should become inactive once it was disabled.
Reproduced on 5.5.0b2, 5.4.0p4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment