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
- "Problem detected while importing the Prefab file" errors on Learning Templates import
- Crash on RaiseException during Socket.BeginConnect in Player when application connection is blocked through commercial firewall
- Decal Projector produces artifacts when the normal and decal are projected in negative z-direction and Normal Blend is set to 1
- Undoing slider field change only resets slider position, doesn't undo the value change
- Precision changes when a tangent is added to a Vertex node
Add comment