Search Issue Tracker
Fixed in 2019.3.X
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
- ‘[…] doesn't have a texture property '_MainTex’’ error when using Gizmos with [MainTexture] attribute
- "undefined symbol: WebView_loadHtml (referenced by top-level compiled C/C++ code)" errors when building a WebGL build
- Script recompiles in Play Mode when Script Changes While Playing option is set to Recompile After Finished Playing and Auto refresh is set to enabled.
- [Windows][Vulkan] Scrambled texture objects are rendered when setting one with Texture2D.UpdateExternalTexture
- NullReferenceException errors appear when using "select half" button
Resolution Note (fix version 2019.3):
Fixed in 2019.3.0a6