-
Notifications
You must be signed in to change notification settings - Fork 37
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
Memory leak python 3.8 #536
Comments
The most recent logs:
|
@danmash Can you provide the command line for the various processes? The logs don't indicate what is happening. Having the commandline for the process that leaked memory would be very helpful to start looking at the problem. |
Closing for now. We can reopen when more info is provided. |
@karthiknadig There's no command; I just use the plugin for black formatting. The black server is running on its own without my interaction. |
@danmash For the process that is leaking memory. I need to know the command line. The black formatter extension starts a server. That server itself spawns sub-processes. It would be a good start to know which specific process is leaking. There are 3 processes there, typically each one has a specific purpose. The CLI column in resource monitor should be helpful. Like this: |
So, do you agree it's one of the extension processes, but you cannot start
investigating until I track which one of these three?
…On Tue, 1 Oct 2024 at 22:50, Karthik Nadig ***@***.***> wrote:
@danmash <https://github.com/danmash> For the process that is leaking
memory. I need to know the command line. The black formatter extension
starts a server. That server itself spawns sub-processes. It would be a
good start to know which specific process is leaking.
image.png (view on web)
<https://github.com/user-attachments/assets/7f59a9f8-d5a4-4f8a-822d-143455f46212>
There are 3 processes there, typically each one has a specific purpose.
The CLI column in resource monitor should be helpful. Like this:
image.png (view on web)
<https://github.com/user-attachments/assets/957021e3-4f06-4d8f-97d2-466860fd3a2c>
—
Reply to this email directly, view it on GitHub
<#536 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA27BUDUAT4U3GAVQNX6TGDZZMKI5AVCNFSM6AAAAABOA2VTYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBXGEZTQNBUGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
That is correct. I need to see which one of the processes it is to investigate. I have not seen any other report of this. |
Type: Bug
I see high memory consumption.
I created an issue in VScode repo microsoft/vscode#228123
But after some investigation, I suppose the reason for the memory leak is the black formater. I'll add logs in the comment.
launch.json
VS Code version: Code 1.93.0 (Universal) (4849ca9bdf9666755eb463db297b69e5385090e3, 2024-09-04T13:02:38.431Z)
OS version: Darwin arm64 23.6.0
Modes:
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: disabled_software
multiple_raster_threads: enabled_on
opengl: disabled_off
rasterization: disabled_software
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: disabled_software
video_encode: disabled_software
webgl: unavailable_software
webgl2: unavailable_software
webgpu: unavailable_software
webnn: disabled_off
Extensions (36)
(2 theme extensions excluded)
A/B Experiments
The text was updated successfully, but these errors were encountered: