Search Issue Tracker
Won't Fix
Votes
3
Found in
2017.4.0f1
2018.3.0a1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1122502
Regression
No
Continuously updating colorMultiplier for a Selectable's colors allocates memory
How to reproduce:
1. Open user-submitted project (ColorTest) and 'SampleScene' scene
2. Enter Play Mode
3. Open the Profiler window and record some frames
4. Select a recorded frame, select Hierarchy view
5. Navigate to PlayerLoop > Update.ScriptRunBehaviourUpdate > ColorMultiplier.Update()
Expected result: no memory is allocated
Actual result: GC.Alloc has a value of 0.9 KB
Reproducible with: 2017.4.20f1, 2018.3.5f1, 2019.1.0b2, 2019.2.0a4
Comments (1)
-
marrr048
Jul 24, 2019 20:54
Hold on - I understand that it might be a low priority issue, but why would you close it because you don't expect to address it yet? Shouldn't it remain open so it doesn't fall through the cracks? If it's closed it will NEVER be addressed. This is not how issue tracking works. You leave it open because it's not fixed yet, and when it eventually does get fixed, then you can close it.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (2019.2.X):
low priority defect, unlikely to be resolved in the near future. Closing for now.