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
- [Linux] Cannot reorder GameObjects in the Hierarchy when the AI Assistant package is installed
- [iOS] Text Input field stops receiving changes when the "Cancel" button is used on the soft keyboard
- [WebGPU] URP RenderGraph RenderPass doesn't clear textures
- Query Builder items display raw code style names instead of human readable labels in search field
- “+” button does nothing and has no functionality when clicked in Human Template "Bone Template" list
Add comment