Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0f1
Issue ID
930144
Regression
No
If mesh was made using mesh.Set*(List) methods it will be never released from memory
Steps to reproduce:
1. Open the attached project
2. Open CanvasRendererSetMeshLeak scene
3. Open Profiler and select Memory
4. Press 'Take Sample: Editor' (Select Detailed (instead of Simple))
5. Expand 'Not Saved / Mesh' tree
6. Find 'Custom UI Mesh'
7. Stop Play mode
8. Repeat steps 5-10 to see 'Custom UI Mesh' never released from memory
Actual results: 'Custom UI Mesh' never released from memory
Expected results: 'Custom UI Mesh' should be released from memory
Reproduced with: 5.5.4p2, 5.6.2p3, 2017.1.0f3, 2017.2.0b3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment