-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
VSCode become laggy after some time and then crash (reason: crashed, code: 132) #212911
Comments
So I tested some things, here what i got:
I dont know if extensions are conflicting each other or there is a problem in this particular extension |
Thanks for identifying that, can you file an issue against the extension too? In case there is anything for us to look at, here's the stack that's producing the listener warnings:
|
I dont think this will work. last extension update was 5 years ago. |
Type: Bug
With verbose mode i see many
potential listener LEAK detected, having XXX listeners already
REFUSES to accept new listeners because it exceeded its threshold by far
SLOW task detected (744ms) but renderer profiling is disabled via 'application.experimental.rendererProfiling'" vscode
And then got crash with:
CodeWindow: renderer process gone (reason: crashed, code: 132)
Verbose log:
vscode_log.txt
I think this is because one of extensions, because on other profile no such problems
VS Code version: Code 1.89.1 (dc96b83, 2024-05-07T05:16:23.416Z)
OS version: Linux x64 6.8.0-76060800daily20240311-generic
Modes:
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
Extensions (19)
A/B Experiments
The text was updated successfully, but these errors were encountered: