Search Issue Tracker
Fixed in 5.3.0
Votes
0
Found in
5.2.0f2
Issue ID
734688
Regression
No
[Canvas] Destroying canvas causes memory leak
Reproduction steps:
1. Open attached project
2. Open and play the "GUILeak" scene
3. There is a "GUILeak" object in the scene that will destroy and recreate object with UI canvas component every frame
4. Check profiler and observe that memory consuption keeps getting higher
NOTE: You can click "Stop Allocations" button on the screen. Memory consumption will stabilize but it will never return to original level.
Comments (2)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
AdamApache
Oct 27, 2015 15:44
This is still extant in 5.2.2.
I have built a simple project which switches between 2 scenes with canvases, and it's still leaking.
Mr_Friendly
Oct 16, 2015 00:14
Any idea what release this will be fixed in? It's causing us quite a problem at the moment.