Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2017.4.20f2
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1136993
Regression
No
GUILayout.Window never releases old windows which causes a memory leak
How to reproduce:
1. Open the attached project "GUILayoutWindowMemLeak.zip" and scene "TestScene"
2. Enter Play Mode
3. Observe the Profiler Window's memory summary
Expected result: the memory used by mono and unity does not continue to increase over time indefinitely (as seen in the profiler's memory summary)
Actual result: used memory increases indefinitely (0.5GB for mono after ~40 minutes)
Reproducible with: 2017.4.24f1, 2018.3.10f1, 2019.1.0b8, 2019.2.0a9
Note: the demo uses windows with different IDs every frame
-
B16B0SS
Nov 11, 2021 13:02
We use a third party tool that makes heavy use of GUILayout.Window to render a canvas. Needless to say, this issue is a problem for us as our computers run out of memory withing a days work. Would be nice for it to be fixed or would like to know of a workaround as this low-priority issue causes a loss of time for us on a daily basis.
-
LT23Live
Sep 16, 2021 15:02
I am also receiving this issue for Unity 2020.3.12 LTS and my coworker reported this with Unity 2020.3.16 LTS. This is really bad for making custom editor windows.
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
- Size of ShadowCaster2D with Casting Source set to a Collider increases when RigidBody2D is attached to the GameObject
- GameObjects with a material derived from a Custom Lighting Surface Shader are displayed as skewed on quads when the Camera's Width and Height properties of the Viewport Rect are lower than 1
- Warning 'Unable to find player assmebly' is thrown when building some Project Templates
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
Resolution Note (2019.3.X):
low priority defects for the moment and unlikely to be fixed for the moment. it's staying in our DB.