Quitting VSCode does not stop Julia(LanguageServer)

[coxackie]

Exactly what the title says. arch linux, code(oss) 1.53.1, julia extension 1.1.23. Here is memory after I have open and closed code 4 times:

Given that every time it costs > 650MB ram, it is a concern...

[pfitzseb]

Can you check the PPIDs for those processes?

[coxackie]

@pfitzseb sorry for not including the legend - the IDs are in the 4th column - before the memory (5th). Not sure if this is what you meant by "check". For more info: if I use neovim built-in lsp with JuliaLanguageServer, it actually gets stopped when I quite neovim.

[pfitzseb]

4th column is process ID, though, right? I'm interested in the parent's process ID (note the extra P in PPID) :)

[coxackie]

ok, so I run top, add ppid, sort by memory:

the 1177 are leftover from previous instances, 19971 is the current one running. 1177 is systemd, 19971 is electron.

[pfitzseb]

Alright. Can you give me the command those processes were started with? htop shows those by default, not sure how to get top to do that.

[coxackie]

here:

[serenity4]

I had the same problem on Ubuntu 20.10, julia-vscode version 1.1.29, VS Code version 1.53.2. Ran out of RAM when 8 julia instances didn't get stopped after switching several times between projects.

[coxackie]

Why this is in the backlog and not being addressed is beyond me.

[davidanthoff]

Why this is in the backlog and not being addressed is beyond me.

We are all volunteers, and so everything ends up on the backlog by default. That just means "hey, would be great if someone wants to tackle this". If someone does start to work on an issue, they move it away from the backlog to indicate that they are working on it.