Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.2.X
Votes
0
Found in
2019.4
2020.3
2020.3.18f1
2021.1
2021.2
2022.1
Issue ID
1371866
Regression
No
Using GUILayout.Window() leads to memory leak
How to reproduce:
1. Open the users’ attached “Test2020.zip” project
2. Open Test > Window Test window
3. In the opened window click the “Repaint” button 20 times
Expected result: Memory usage to not increase
Actual result: Memory usage keeps increasing
Reproducible with: 2019.4.31f1, 2020.3.21f1, 2021.1.26f1, 2021.2.0f1, 2022.1.0a5
Not reproducible with: 2022.1.0a6, 2022.1.0a13
Notes:
- To see the memory increase use Profiler with Memory module or Task Manager/Activity monitor
- Memory usage can also be increased by resizing the “Window Test” window
- To increase the memory usage further just repeat step 3 multiple times
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
- A vertical graphical artifact appears on Android Player when clearing Z & Stencil Buffer and running with OpenGLES3 Graphics API
- Player crashes when built with IL2CPP Scripting backend
- TextMeshPro package throws multiple Shader errors when importing TMP Essential Resources
- Package Manager search text field has no validation and leads to Editor freezes
- PlayerLoop.SetPlayerLoop() function is ignored when playing game in Player
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a6
Resolution Note (fix version 2021.2):
Fixed in 2021.2.17f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.33f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.38f1