Search Issue Tracker
Active
Votes
0
Found in
2018.3.0f2
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Hub] No button to add Platform support to installed Unity versions
- GameObject selection inside Prefab causes Editor lag/freeze
- Camera does not Render a Video Player when Cameras Culling Mask is set to anything except "Everything"
- [iOS][Editor]Legacy Launch Images iPhone 6.5 Landscape resolution mislabelled in Player Settings/Splash Image
- The Marker does not Run and gets Skipped when running in Reverse
Add comment