Search Issue Tracker
Fixed in 2019.3
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1126862
Regression
No
Memory leaks are introduced when calling Texture2D.GenerateAtlas
How to reproduce:
1. Open the "SampleScene" Scene in the attached "UVPacking.zip" Project
2. Enter Play Mode
3. If the Editor does not freeze - Exit play mode and repeat from step 3 (it can happen after repeating from 1 to 5+ times)
4. Inspect the Editor's Memory usage in the Task Manager or any other external Monitoring tool
Expected Behavior: The Editor generates the Atlas and does not freeze
Actual Behavior: The Editor starts leaking Memory at around 700mb/sec rate and eventually Crashes
Reproducible with: 2017.4.20f2, 2018.3.6f1, 2019.1.0b3, 2019.2.0a5
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The main loop is never scheduled in 2018.x when build starts in background
- EditorApplication.isPlaying value is true when calling it in OnDisable() and Entering Play Mode
- "Entering Playmode with Reload Domain disabled" log appears when Configurable Enter Play Mode is enabled and pressing Play
- [2D] [Lost Crypt Demo] null texture passed to GUI.DrawTexture warning when opening demo
- Editor freezes and silently crashes when an object with SerializeReference is assigned an object with System.Obsolete attribute
Resolution Note (fix version 2019.3):
Fixed in 2019.3.0a6