Search Issue Tracker
Fixed in 2018.3
Votes
0
Found in
2017.4.6f1
Issue ID
1058621
Regression
No
[Memory] Unity leaks memory and eventually crashes when selecting any UI batch in the profiler
How to reproduce:
1. Create a new Project
2. In the Hierarchy Window create a new Image Object
3. Open the Profiler Window and Enter Play mode
4. In the Profiler Window click UI -> All Canvases -> Canvas -> Batch 0
5. Open and observe the Task Manager
Expected result: The profiler doesn't leak memory
Actual result: Clicking on any UI batch element slowly leaks memory and eventually crashes Unity
Reproduced in: 2018.3.0a4, 2018.2.0f2, 2018.1.8f1, 2017.4.6f1, 2017.2.3p2, 2017.1.4p2
Note: Unity has to be the active window for the bug to reproduce
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The main loop is never scheduled in 2018.x when build starts in background
- EditorApplication.isPlaying value is true when calling it in OnDisable() and Entering Play Mode
- "Entering Playmode with Reload Domain disabled" log appears when Configurable Enter Play Mode is enabled and pressing Play
- [2D] [Lost Crypt Demo] null texture passed to GUI.DrawTexture warning when opening demo
- Editor freezes and silently crashes when an object with SerializeReference is assigned an object with System.Obsolete attribute
Add comment