# Julia process staying after closing VSCode

**URL:** <https://discourse.julialang.org/t/julia-process-staying-after-closing-vscode/95789>\
**Category:** General Usage\
**Tags:** vscode\
**Created:** [March 9, 2023, 9:21am UTC](https://discourse.julialang.org/t/julia-process-staying-after-closing-vscode/95789 "2023-03-09T09:21:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![TheLateKronos](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/thelatekronos/32/12824_2.png) [@TheLateKronos](https://discourse.julialang.org/u/TheLateKronos)\
**Post date:** [March 9, 2023, 9:21am UTC](https://discourse.julialang.org/t/julia-process-staying-after-closing-vscode/95789/1 "2023-03-09T09:21:05Z")

</div>

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

 ![image](https://global.discourse-cdn.com/julialang/original/3X/1/6/16ba095741f36d757846bed04a43e797d6765f71.png)  
Information about the process. The “Command Line” options clearly indicate that the process was started by VSCode, which is closed:  
 ![image](https://global.discourse-cdn.com/julialang/original/3X/3/c/3c05092c608967cdd339102282f1a4cd7daba0d2.png)  
(Scrolling to the right to show full line:)  
 ![image](https://global.discourse-cdn.com/julialang/original/3X/a/3/a3716dd3fb0c64961b7eb5d1c4615c493800aefa.png)  
 ![image](https://global.discourse-cdn.com/julialang/original/3X/8/f/8f7abcac72a64e4727a80c42bbf815b6f27a65e9.png)

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

---

<div class="post-metadata">

**Author:** ![albheim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/albheim/32/34660_2.png) [@albheim](https://discourse.julialang.org/u/albheim)\
**Post date:** [March 9, 2023, 10:09am UTC](https://discourse.julialang.org/t/julia-process-staying-after-closing-vscode/95789/2 "2023-03-09T10:09:01Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![TheLateKronos](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/thelatekronos/32/12824_2.png) [@TheLateKronos](https://discourse.julialang.org/u/TheLateKronos)\
**Post date:** [March 9, 2023, 12:31pm UTC](https://discourse.julialang.org/t/julia-process-staying-after-closing-vscode/95789/3 "2023-03-09T12:31:49Z")

</div>

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…

---

<div class="post-metadata">

**Author:** ![lrnv](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lrnv/32/19373_2.png) [@lrnv](https://discourse.julialang.org/u/lrnv)\
**Post date:** [March 9, 2023, 12:45pm UTC](https://discourse.julialang.org/t/julia-process-staying-after-closing-vscode/95789/4 "2023-03-09T12:45:39Z")

</div>

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…).