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
- “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
Add comment