Julia process staying after closing VSCode

General Usage
1

After closing VSCode (and all terminals), a Julia process sticks around and hogs 2 GB of RAM:

image
image2560×1440 506 KB

Information about the process. The “Command Line” options clearly indicate that the process was started by VSCode, which is closed:
image
image2546×942 142 KB

(Scrolling to the right to show full line:)
image
image2558×56 12.3 KB

image
image2192×56 13.1 KB

This is not ideal. Any idea why, and if I should file a bug report?

2

I used to have similar problems, had to go and clean up julia processes every now and then which all seemed related to vscode.

I assumed it was processes I killed through the vscode interface because they were just hanging, and then they didn’t get actually killed but just detached from vscode somehow. But I never really investigated it, and I haven’t noticed it recently so haven’t thought about it in a while.

1 Like
3

So it could be related to the fact that when I killed a GLMakie window that was not responding, the julia process seemed to die (terminal dissapeared, window closed), but in fact the julia process survived somehow…

4

On Windows here, VS Code process management is also a problem.

For example (unrelated to Julia), the Latex Workshop extension regularly leaves pdflatex processes and perl processes hanging around after closing VS Code. Since I spend my life opening repositories with latex documents, I end up having to manually kill them once in a while (the other day I had 7 perl.exe running for nothing…).