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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Add comment