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.
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
- Custom ScriptableObject asset in the project setting are not well deserialized during the Reimport All process
- Fixing Message Loss in UMPE During Domain Reload
- The Editor freezes when ScheduleReadOnly of IJobParallelForTransform with dependency is used
- Text is truncated in the Inspector when the display scale is set to 150%
- CancellationTokenSource(<timeout>) has incorrect cancellation status when used in WebGL Player
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.