Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0a5
Issue ID
1063137
Regression
No
2018.3: GraphicRegistery.RegisterGraphicForCanvascauses GCAlloc always
To reproduce:
1. Open user attached project
2. Make a Windows Standalone build
3. Run standalone build
4. Connect Unity Profiler
5. Switch from "Timeline" to "Hierarchy" in Profiler
6. Search for "TestCode"
Observe TestCode contains 364bytes GC Alloc, causes by GraphicRegistery.RegisterGraphicForCanvas.
Actual: GraphicRegistery.RegisterGraphicForCanvas allocates memory always.
Expected: GraphicRegistery.RegisterGraphicForCanvas allocates memory when called the first time only.
Reproducible: 2018.3.0a5, 2018.2.0f2, 2018.1.9f1
Comments (1)
-
Quasimodem
Oct 18, 2020 22:07
Can I request that this be reopened? Allocations are a very big deal on low-end hardware like the Switch, no matter how small. This one adds a lot of burden onto systems like damage kickers where you need to enable/disable UI at regular intervals.
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
- "ArgumentOutOfRangeException" and UITK is rendered incorrectly when building in WebGL with Native C/C++ Multithreading enabled
- Changing Transform.position.z per-frame should not affect Rigidbody2D interpolation.
- Cancelling a build during "Incremental Player Build" step returns wrong BuildReport result
- Log “Found 1 leak(s) from callstack:“ is present in Editor when Leak Detection Level is set to "Enabled"
- Content in "Asset PostProcessors" Section Not Vertically Centered in Box
Resolution Note (2018.3.X):
low priority defect, unlikely to be resolved in the near future. Closing for now.