New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Potential leak detected in decorations #63467
Comments
Found while looking into #63467 There's potential leak for `DecorationCSSRules`. Currently we only dipose of them if `hasContent` is true, which I'm not sure guarantees that these classes are truely non-disposable With this change, we always dispose of them. At worst, these extra dispose call should be noops
d37f7c1 looked into one potential leak. Not sure if this was the one causing the issue or not since I can't reliably repo the problem |
the code lens widgets don't leak but each widget is a listener which is maybe not the smartest... |
Pushed one more change to fix an actual leak, but that grows with the number of editors only. |
Closing this and seeing if this occurs again... Per editor code is now just 1 listener, not one per lens. Unsure what the other 500 listeners are... |
Issue Type: Bug
While working with VS Code today, I saw these two potential leaks in the dev console:
Sorry, no clear repo steps. I first noticed this when I was in a side-by-side diff view and trying to stage a change the selected range. This operation took quite a while.
VS Code version: Code - Insiders 1.30.0-insider (ebe9ea8, 2018-11-19T19:59:44.607Z)
OS version: Darwin x64 18.2.0
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: enabled
rasterization: enabled
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
Extensions (30)
(16 theme extensions excluded)
The text was updated successfully, but these errors were encountered: