Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2018.1.0a1
2018.3.0a1
2019.1.0a1
2019.2.0a1
2019.3.0a1
2019.3.0a9
Issue ID
1170031
Regression
No
Unity leaks memory when adding/removing breakpoints while debugging with Visual Studio
How to reproduce:
1. Open the "VS_Leak.zip" project
3. Open the "NewBehaviurScript.cs" script
4. Attach Unity Debugger via Visual Studio
5. Open the Task Manager
6. In VS, keep adding/removing a breakpoint on one line
7. Observe the rising RAM usage
Actual result: Unity leaks memory. (gif attached)
Expected result: Unity doesn't leak memory.
Reproducible with: 2019.3.0a10, 2019.2.0b10, 2019.1.10f1, 2018.4.4f1, 2018.1.9f, 2017.4.30f1.
Notes:
The leak doesn't reproduce if using C# 3.5.
The leak is a lot smaller in Unity 2019.3 (leaks around 0.1MB per click)
--------------------------------------------
Fixed in 2020.1.0a2. 2019.3.0b3.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ‘[…] doesn't have a texture property '_MainTex’’ error when using Gizmos with [MainTexture] attribute
- "undefined symbol: WebView_loadHtml (referenced by top-level compiled C/C++ code)" errors when building a WebGL build
- Script recompiles in Play Mode when Script Changes While Playing option is set to Recompile After Finished Playing and Auto refresh is set to enabled.
- [Windows][Vulkan] Scrambled texture objects are rendered when setting one with Texture2D.UpdateExternalTexture
- NullReferenceException errors appear when using "select half" button
Add comment