# High CPU Usage on Startup - VSCode OSX

**URL:** <https://discourse.julialang.org/t/high-cpu-usage-on-startup-vscode-osx/33280>\
**Category:** General Usage\
**Tags:** vscode\
**Created:** [January 12, 2020, 11:05pm UTC](https://discourse.julialang.org/t/high-cpu-usage-on-startup-vscode-osx/33280 "2020-01-12T23:05:58Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![loki](https://avatars.discourse-cdn.com/v4/letter/l/3be4f8/32.png) [@loki](https://discourse.julialang.org/u/loki)\
**Post date:** [January 12, 2020, 11:05pm UTC](https://discourse.julialang.org/t/high-cpu-usage-on-startup-vscode-osx/33280/1 "2020-01-12T23:05:58Z")

</div>

Hello,

I was forced to switch over from Atom to VSCode and noticed some strange behavior when starting VSCode. Whenever I start up VSCode a Julia process is created that uses 100% CPU usage even before Julia/REPL is started. I’ve seen else where that this is possibly due to the Julia Extension compiling my packages in the background but when I close VSCode this process is still running. If I reopen the program, another process is created in addition to the previous one requiring 100% CPU usage. It seems the only way to stop these is by preforming a restart of my computer.

Is there a way to prevent this from occurring? Is it possible to configure VSCode be similar to Atom such that Julia processes are only created when I run start Julia/REPL and can be killed by running exit()?

I am currently running Julia 1.3.0 and VSCode 1.41.1 on OSX 10.15.2.

---

<div class="post-metadata">

**Author:** ![ufechner7](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ufechner7/32/51363_2.png) [@ufechner7](https://discourse.julialang.org/u/ufechner7)\
**Post date:** [January 13, 2020, 1:05am UTC](https://discourse.julialang.org/t/high-cpu-usage-on-startup-vscode-osx/33280/2 "2020-01-13T01:05:06Z")

</div>

Just give vscode the time to index your packages. Let it run over night. Its a kind-of-bug with a simple work around.

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [January 13, 2020, 2:05am UTC](https://discourse.julialang.org/t/high-cpu-usage-on-startup-vscode-osx/33280/3 "2020-01-13T02:05:02Z")

</div>

Hm, what is really wrong, though, is that this process hangs around when you close VS Code, that should definitely kill it. Could you open an issue?

I should also add that @ZacLN and I are currently working on fixing this whole load time mess. We’re making progress 🙂 It is our number 1 priority right now.

---

<div class="post-metadata">

**Author:** ![loki](https://avatars.discourse-cdn.com/v4/letter/l/3be4f8/32.png) [@loki](https://discourse.julialang.org/u/loki)\
**Post date:** [January 13, 2020, 2:18am UTC](https://discourse.julialang.org/t/high-cpu-usage-on-startup-vscode-osx/33280/4 "2020-01-13T02:18:26Z")

</div>

@davidanthoff  
Of course, though where is the best place to open an issue for this? I am happy that you guys are working on this!

Since this is indexing my packages, this should only occur after I add new packages rather than every time the program is reopened?

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [January 13, 2020, 2:25am UTC](https://discourse.julialang.org/t/high-cpu-usage-on-startup-vscode-osx/33280/5 "2020-01-13T02:25:31Z")

</div>

Best place to report bugs is at [GitHub - julia-vscode/julia-vscode: Julia extension for Visual Studio Code](https://github.com/julia-vscode/julia-vscode).

Yes, this should be a one-time problem until the index is created.

---

<div class="post-metadata">

**Author:** ![kdzhang](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kdzhang/32/11696_2.png) [@kdzhang](https://discourse.julialang.org/u/kdzhang)\
**Post date:** [March 8, 2020, 7:46pm UTC](https://discourse.julialang.org/t/high-cpu-usage-on-startup-vscode-osx/33280/7 "2020-03-08T19:46:12Z")

</div>

I actually have the same issue, since last week. I have to kill the julia process manually every time, and the CPU load is almost 100%. Since I have used VSCode julia for more than 1 year, and I have not updated Julia or Julia packages recently, I do not expect the re-indexing to take so long?

I am currently running Julia 1.3.0 and VSCode 1.42.1 on OSX 10.15.3, and VSCode-Julia 0.14.13.

---

<div class="post-metadata">

**Author:** ![Thibaut\_Lamadon](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/thibaut_lamadon/32/14309_2.png) [@Thibaut\_Lamadon](https://discourse.julialang.org/u/Thibaut_Lamadon)\
**Post date:** [April 24, 2020, 6:25pm UTC](https://discourse.julialang.org/t/high-cpu-usage-on-startup-vscode-osx/33280/8 "2020-04-24T18:25:52Z")

</div>

Same problem for me with julia 1.4, makes VSCode unusable, I did let it run for hours, it just never stops.

---

<div class="post-metadata">

**Author:** ![jmboehm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jmboehm/32/2263_2.png) [@jmboehm](https://discourse.julialang.org/u/jmboehm)\
**Post date:** [April 24, 2020, 7:20pm UTC](https://discourse.julialang.org/t/high-cpu-usage-on-startup-vscode-osx/33280/9 "2020-04-24T19:20:57Z")

</div>

Same here.

In addition, I face the problem that sometimes, out of the blue, Ctrl+Enter executes the code in a new REPL. I have no idea what’s causing this and can therefore not reproduce it. I feel that it’s kind of unhelpful to report an issue without a MWE…