Search Issue Tracker
Won't Fix
Votes
0
Found in
5.4.0p1
Issue ID
831335
Regression
Yes
Adding "Canvas Group" component to "Canvas" results in slow performance when child game objects are constantly re-parented
Any child being re-parented fires off a message to its CanvasGroup, the CanvasGroup then broadcasts a message to all of its children, this message causes each child to work its way up the hierarchy, calling GetComponent at each level, trying to figure out how it should handle its canvas group registration which results in slow performance.
Steps to reproduce:
1. Open attached project
2. Open "CanvasGroupMakesSetSiblingIndexReallySlow" scene
3. Select GameObject->Canvas in hierarchy
4. Add component "Canvas Group"
5. Start play mode
-Performance drops from 90fps to 40fps
Reproduced on: 5.5.0b5, 5.4.1f1
Not reproduced on: 5.3.6p5
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
Add comment