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
- "Report is from another project" popup warning is shown on domain reload when Project Auditor was previously ran in a different project
- Addressables Analyzer flags duplicate resource references from ScriptableObjects incorrectly when the corresponding field has been removed
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
Add comment