Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.3.0a2
2019.3.0a3
Issue ID
1163464
Regression
No
[IMGUI Debugger] Memory leaking when hovering over IMGUI elements in debugger or in inspected window
To reproduce:
1. Open any project
2. Open IMGUI Debugger and select Inspector debugging
3. In IMGUI Debugger, keep clicking instruction OR keep hovering Inspector window elements when instruction is selected
4. Observe the memory leak via Task manager / Profiler
Result: memory is leaking (each click / hover leaks, 0.4-1 Mb)
Reproduced in: 2019.3.0a2, 2019.3.0a6
Note1: IMGUI Debugger implemented in 2019.3.0a2
Note2: there were occasions where memory wouldn't stop leaking until IMGUI debugger is defocused, however I couldn't find exact steps to reproduce it 100%.
one of methods is getting back to idle editor after a minute or two of not being focused on editor
Note3: behavior reproducible with most of the windows, however, Inspector seems to be easiest to reproduce leak on
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
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Resolution Note (2019.3.X):
low priority defect and unlikely to be fix.