Search Issue Tracker
Fixed in 2017.2.0f3
Votes
1
Found in
5.6.0f3
Issue ID
899441
Regression
Yes
Enabling MaskableGraphic will cause GC spikes if Canvas contains UI elements
Reproduction Steps:
1. Import attached project.
2. Open "test" scene.
3. Enter Play mode.
4. In Hierarchy, drag "Filled Simple 1" from Assets folder into Canvas.
5. In Profiler, observe GC Allocated in Memory.
6. Activate Image objects in Canvas.
7. Drag "Filled Simple 1" into Canvas again.
8. Observe GC Allocated.
Expected result: GC Allocated spikes should not become larger.
Actual result: GC Allocated spikes become 10 times larger.
Reproducible with: 5.6.0f3, 2017.1.0b1
Not reproducible with: 5.5.3p1
Regression introduced in: 5.6.0b8
Comments (1)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Eldirfar
Aug 12, 2017 00:50
Any patch for 5.6?