Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0b3
Issue ID
995604
Regression
Yes
Console windows is leaking memory when you outputting a lot of data into Console
Steps to reproduce:
1. Open the attached project
2. Open the test.unity scene
3. Play the scene
4. Open the task manager and observe how memory is increasing
5. Stop the scene and clear the Console Window
6. Memory consumption did not change
Actual results: Console window is leaking a memory and has no way to clear it
Expected results: Console window should not leak a memory
Reproduced with: 5.6.4p4, 2017.1.3p1, 2017.2.1p4, 2017.3.1p1, 2018.1.0b7, 2018.2.0b11
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (2019.2.X):
It is expected that when a large file is opened, it takes significant amount of memory to open that file. Verified that the extra memory used by Unity is pretty much the same when we open the same log file with other applications like wordpad, which suggests that there isn't any memory leak