# VS Code Extension woes

**URL:** <https://discourse.julialang.org/t/vs-code-extension-woes/5872>\
**Category:** Offtopic\
**Created:** [September 13, 2017, 5:26pm UTC](https://discourse.julialang.org/t/vs-code-extension-woes/5872 "2017-09-13T17:26:33Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sean\_McBane](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sean_mcbane/32/4580_2.png) [@Sean\_McBane](https://discourse.julialang.org/u/Sean_McBane)\
**Post date:** [September 13, 2017, 5:26pm UTC](https://discourse.julialang.org/t/vs-code-extension-woes/5872/1 "2017-09-13T17:26:33Z")

</div>

Hi all, I’ve been editing my Julia code in vim happily but I wanted to try out VS Code with the plugin to see how I liked it. However, while syntax highlighting and autoindentation works fine, the extension seems to be stuck loading the language server (for linting, I guess?); the bottom left always reads “Julia: starting up”. It’s taking up 100% of one CPU and continuously taking up more memory, until it crashes (every 5 minutes or so). The debug tools in Code show that it’s exhausting the JS heap.

Has anyone else seen these problems, and if so how did you fix it? I’m running the latest released versions of both Julia and Code.

---

<div class="post-metadata">

**Author:** ![rdeits](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/rdeits/32/286_2.png) [@rdeits](https://discourse.julialang.org/u/rdeits)\
**Post date:** [September 13, 2017, 5:33pm UTC](https://discourse.julialang.org/t/vs-code-extension-woes/5872/2 "2017-09-13T17:33:07Z")

</div>

This might be related to [https://github.com/JuliaEditorSupport/julia-vscode/issues/255](https://github.com/JuliaEditorSupport/julia-vscode/issues/255) (there’s a possible fix at the bottom of that issue discussion)

---

<div class="post-metadata">

**Author:** ![tkoolen](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkoolen/32/1603_2.png) [@tkoolen](https://discourse.julialang.org/u/tkoolen)\
**Post date:** [September 13, 2017, 6:37pm UTC](https://discourse.julialang.org/t/vs-code-extension-woes/5872/3 "2017-09-13T18:37:16Z")

</div>

The main symptom of that issue is a “Julia: busy” message, not “Julia: starting up” though. It might be worth opening a new issue.

---

<div class="post-metadata">

**Author:** ![ArchieCall](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/archiecall/32/206_2.png) [@ArchieCall](https://discourse.julialang.org/u/ArchieCall)\
**Post date:** [September 13, 2017, 7:13pm UTC](https://discourse.julialang.org/t/vs-code-extension-woes/5872/4 "2017-09-13T19:13:21Z")

</div>

I switched over the VS code from Atom and experience the same issues with busy all the time. That being said it seems to be more responsive than Atom. and do not contemplate going back.

---

<div class="post-metadata">

**Author:** ![ZacLN](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/zacln/32/2748_2.png) [@ZacLN](https://discourse.julialang.org/u/ZacLN)\
**Post date:** [September 13, 2017, 8:01pm UTC](https://discourse.julialang.org/t/vs-code-extension-woes/5872/5 "2017-09-13T20:01:05Z")

</div>

Do you think you could follow the instructions [here](https://github.com/JuliaEditorSupport/julia-vscode/wiki/Manually-turning-on-the-LanguageServer-debugger) to turn on logging and open an issue with the debugging output?

---

<div class="post-metadata">

**Author:** ![Sean\_McBane](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sean_mcbane/32/4580_2.png) [@Sean\_McBane](https://discourse.julialang.org/u/Sean_McBane)\
**Post date:** [September 13, 2017, 8:21pm UTC](https://discourse.julialang.org/t/vs-code-extension-woes/5872/6 "2017-09-13T20:21:20Z")

</div>

I’ll do this now. I don’t think from the symptoms that it’s due to the issue that @rdeits linked above. Also, I just tested on my Windows laptop instead of my Linux workstation and everything worked fine; I don’t know how significant that is but I’ll mention it in the issue.

---

<div class="post-metadata">

**Author:** ![Sean\_McBane](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sean_mcbane/32/4580_2.png) [@Sean\_McBane](https://discourse.julialang.org/u/Sean_McBane)\
**Post date:** [September 13, 2017, 8:34pm UTC](https://discourse.julialang.org/t/vs-code-extension-woes/5872/7 "2017-09-13T20:34:51Z")

</div>

@ZacLN I tried to follow the instructions (edited “main.jl” in the language server subdirectory to call with debug mode = true), but I don’t see any output in Code. I think your instructions must have been written for an older version, the only drop down menu options I have for output are ‘Search’, ‘Tasks’, ‘Extensions’, and ‘Git’. Is there an easy way to have the language server write debug output to a file instead, perhaps?

---

<div class="post-metadata">

**Author:** ![ZacLN](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/zacln/32/2748_2.png) [@ZacLN](https://discourse.julialang.org/u/ZacLN)\
**Post date:** [September 13, 2017, 8:55pm UTC](https://discourse.julialang.org/t/vs-code-extension-woes/5872/8 "2017-09-13T20:55:44Z")

</div>

Hmm thats very strange there really ought to be some output there even without debug mode enabled. Did you restart vscode?

A more basic test could be to cd to `LanguageServer` from julia (in `julia-vscodeinstalldir/scripts/languageserver/packages/LanguageServer`) manually include the package (`include("src/LanguageServer.jl")`) and try running the tests (`include("test/runtests.jl")`)

---

<div class="post-metadata">

**Author:** ![ArchieCall](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/archiecall/32/206_2.png) [@ArchieCall](https://discourse.julialang.org/u/ArchieCall)\
**Post date:** [September 13, 2017, 9:11pm UTC](https://discourse.julialang.org/t/vs-code-extension-woes/5872/9 "2017-09-13T21:11:52Z")

</div>

This is my line 26 - I am on Windows 10

```julia
server = LanguageServerInstance(STDIN, conn, ls_debug_mode, Base.ARGS[1])

```

How do I set it to True?

---

<div class="post-metadata">

**Author:** ![Sean\_McBane](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sean_mcbane/32/4580_2.png) [@Sean\_McBane](https://discourse.julialang.org/u/Sean_McBane)\
**Post date:** [September 13, 2017, 9:12pm UTC](https://discourse.julialang.org/t/vs-code-extension-woes/5872/10 "2017-09-13T21:12:37Z")

</div>

@ArchieCall Just change `ls_debug_mode` to `true`… I left a comment to remind myself what the original was.

---

<div class="post-metadata">

**Author:** ![Sean\_McBane](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sean_mcbane/32/4580_2.png) [@Sean\_McBane](https://discourse.julialang.org/u/Sean_McBane)\
**Post date:** [September 13, 2017, 9:13pm UTC](https://discourse.julialang.org/t/vs-code-extension-woes/5872/11 "2017-09-13T21:13:47Z")

</div>

@ZacLN Ok, I did find an error running the tests as described; the error line reads

```
INFO: ERROR: (unhandled task failure): KeyError: key "Content-Length" not found

```

That’s the only error.

Edit: Ran the same check on my Windows laptop, get the same error, but the language server _does_ start up successfully, so it’s not causing the behavior I’m observing.

---

<div class="post-metadata">

**Author:** ![ArchieCall](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/archiecall/32/206_2.png) [@ArchieCall](https://discourse.julialang.org/u/ArchieCall)\
**Post date:** [September 13, 2017, 9:38pm UTC](https://discourse.julialang.org/t/vs-code-extension-woes/5872/12 "2017-09-13T21:38:22Z")

</div>

I got the true line enabled. Just by virtue of doing this the Julia: busy indicator is now almost always showing as Julia: ready. Much better.

There is plenty of debug output now showing in the Output panel.

The intellisense/tips stuff seems to work only intermittently. Maybe better than before, but not much.

Do you want me to paste this output somewhere?