# Stray Julia processes (with high cpu usages)

**URL:** <https://discourse.julialang.org/t/stray-julia-processes-with-high-cpu-usages/33303>\
**Category:** General Usage\
**Created:** [January 13, 2020, 3:04pm UTC](https://discourse.julialang.org/t/stray-julia-processes-with-high-cpu-usages/33303 "2020-01-13T15:04:14Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![longemen3000](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/longemen3000/32/7298_2.png) [@longemen3000](https://discourse.julialang.org/u/longemen3000)\
**Post date:** [January 18, 2020, 9:55pm UTC](https://discourse.julialang.org/t/stray-julia-processes-with-high-cpu-usages/33303/13 "2020-01-18T21:55:22Z")

</div>

i will put my two cents and bet that it is the language server of the VSCode Plugin. it takes a lot of time to index the packages (variable, but over half an hour), and when its doing that, it takes a lot of resources.

> [@VS Code extension v0.13.0 release candidate](https://discourse.julialang.org/t/vs-code-extension-v0-13-0-release-candidate/32360/28):
>
> Not stored on disc means that it has yet to been indexed and cached by SymbolServer. This is only done once per package version, so the long wait is only done once. Once it has been cached it will be fine. If it completes, it says “store set”. There does seem to be a fairly large slowdown in performance in the latest VSCode extension.

---

_[View the full topic](https://discourse.julialang.org/t/stray-julia-processes-with-high-cpu-usages/33303)._