Search Issue Tracker
Fixed
Votes
0
Found in
4.6.0f3
Issue ID
652749
Regression
No
Memory is not fully released after destroying Texture2D
To Reproduce:
1. Open the attached project and Play.
2. Click 'Test 2'
3. Wait until the test is completed and click 'Test 2'
4. Unity crashes with an out of Memory error
Seems that memory isn't fully cleared after calling DestroyImmediate, if it's called after creating each texture, after running the test Textures use ~7mb, but mono still uses up around 1.2GB of memory which is never released (after running Test 2 once).
Memory usage after running 'Test 2' once in editor:
4.5.1p5: 1.47GB
5.0.0b21: 350MB
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 when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Add comment