Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2017.4.X, 2018.3.X
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
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
ScientificGames_Chandramohan
Jun 19, 2020 10:28
Project link?