Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.3.0a1
2018.3.0b9
Issue ID
1126769
Regression
No
Memory is leaking when using SetFloat() to update Shader properties with Shader.PropertyToID()
To reproduce:
1. Open attached project
2. Enter Play mode
3. Observe memory leaking via Task Manager or other applicable resource monitoring tool
Actual result: memory is leaking when updating Shader properties with SetFloat()
Reproduced in: 2018.3.0a1, 2018.3.0b10
Not reproduced in: 2017.4.20f1, 2018.3.0b11, 2018.3.6f1, 2019.1.0b3, 2019.2.0a5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
Add comment