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
- Bloom and Exposure Artifacting around GameObject appears when setting Scale of Z Axis to 0
- [Android][IL2CPP][ARMv7] Struct field value corrupts when invoking a generic delegate with a large struct by value
- Highlights persist throughout Options Panels in the Rendering Debugger Window
- Typing numbers in Matrix node’s numeric fields stretches Node
- Streaming is misspelled as "Steaming" in "Enable GPU Streaming" and "Enable Disk Streaming" tooltpis
Add comment