Search Issue Tracker
Fixed in Unity 2019.1
Votes
0
Found in
2017.4.6f1
Issue ID
1090901
Regression
No
Memory leak when using SetPropertyBlock and EnableKeyword in OnRenderObject
To reproduce:
1. Download project "RenderingMemoryLeaks.zip" and open in Unity
2. Open "Scene" scene
3. Enter Play mode
4. Observe that NativeUsed is drastically going up
5. Build & Run project
6. Observe that NativeUsed is drastically going up like in the Unity Editor
Notes:
- This issue appears on both Windows and macOS
- This issue reproduces on Standalone and Nintendo Switch
Reproduced on Unity 2017.4.0f1, 2017.4.13f1, 2018.1.9f2, 2018.2.12f1, 2018.3.0b6 and 2019.1.0a5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [XR][Vulkan] LWRP using stereo instancing renders to only one eye when SRP batcher is enabled
- Unity Unit Tests process terminated in CLI mode because of XR Manager
- Resetting a Preset removes its type and renders it useless
- [LWRP] Add to list button gives empty list when trying to add features to the Forward Renderer
- Inspector blinks / flickers once when Inspector is visible, any object from the Hierarchy is selected and a script is recompiled
Add comment