Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
4.5.0f6
Issue ID
611867
Regression
No
Memory is not freed by 'Object.Destroy' when returning to edit mode
To reproduce:
1. Open the attached project
2. Open scene Test. It contains gameobjects with a script that creates a mesh and allocates vertices and triangles to is. It also destroys the mesh OnDestroy.
3. Enter/leave play mode and inspect the memory usage via Task Manager - it is growing with each play - memory is not being freed
Freeing the memory earlier than OnDestroy works fine.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Add comment