# REPL in VS Code stalling overnight

**URL:** <https://discourse.julialang.org/t/repl-in-vs-code-stalling-overnight/63976>\
**Category:** VS Code\
**Created:** [July 3, 2021, 7:02am UTC](https://discourse.julialang.org/t/repl-in-vs-code-stalling-overnight/63976 "2021-07-03T07:02:30Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bardo](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bardo/32/21601_2.png) [@Bardo](https://discourse.julialang.org/u/Bardo)\
**Post date:** [July 3, 2021, 7:02am UTC](https://discourse.julialang.org/t/repl-in-vs-code-stalling-overnight/63976/1 "2021-07-03T07:02:30Z")

</div>

Leaving the session open, the REPL window regularly freezes with an empty screen and the cursor about in the middle.  
Any remedy?  
(Win10, latest VS Code and Julia)

---

<div class="post-metadata">

**Author:** ![ClarkGuilty](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/clarkguilty/32/21883_2.png) [@ClarkGuilty](https://discourse.julialang.org/u/ClarkGuilty)\
**Post date:** [July 3, 2021, 7:27pm UTC](https://discourse.julialang.org/t/repl-in-vs-code-stalling-overnight/63976/2 "2021-07-03T19:27:22Z")

</div>

I have the same problem in VS codium in Arch Linux. No remedy so far.

---

<div class="post-metadata">

**Author:** ![ess3sq](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ess3sq/32/26834_2.png) [@ess3sq](https://discourse.julialang.org/u/ess3sq)\
**Post date:** [July 3, 2021, 10:47pm UTC](https://discourse.julialang.org/t/repl-in-vs-code-stalling-overnight/63976/3 "2021-07-03T22:47:04Z")

</div>

Something similar happens on Atom/Juno. The REPL window randomly freezes and I have to kill Julia. Not sure if that’s related to the VS code issue but I thought I’d weigh in anyway.

---

<div class="post-metadata">

**Author:** ![Bardo](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bardo/32/21601_2.png) [@Bardo](https://discourse.julialang.org/u/Bardo)\
**Post date:** [July 4, 2021, 7:05am UTC](https://discourse.julialang.org/t/repl-in-vs-code-stalling-overnight/63976/4 "2021-07-04T07:05:03Z")

</div>

Hmm, never happened during work, but this would hint at a problem with Julia itself?

---

<div class="post-metadata">

**Author:** ![Bardo](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bardo/32/21601_2.png) [@Bardo](https://discourse.julialang.org/u/Bardo)\
**Post date:** [July 5, 2021, 6:33am UTC](https://discourse.julialang.org/t/repl-in-vs-code-stalling-overnight/63976/5 "2021-07-05T06:33:27Z")

</div>

BTW, the powershell pane freezes as well.

---

<div class="post-metadata">

**Author:** ![johnh](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/johnh/32/3615_2.png) [@johnh](https://discourse.julialang.org/u/johnh)\
**Post date:** [July 5, 2021, 6:38am UTC](https://discourse.julialang.org/t/repl-in-vs-code-stalling-overnight/63976/6 "2021-07-05T06:38:57Z")

</div>

Stupid question - does this happen when your laptop suspends itself?  
The first thing I would do is adjust the power saving settings.

---

<div class="post-metadata">

**Author:** ![Bardo](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bardo/32/21601_2.png) [@Bardo](https://discourse.julialang.org/u/Bardo)\
**Post date:** [July 5, 2021, 6:46am UTC](https://discourse.julialang.org/t/repl-in-vs-code-stalling-overnight/63976/7 "2021-07-05T06:46:02Z")

</div>

No, laptop is on mains, I move the mouse and log in.

---

<div class="post-metadata">

**Author:** ![ess3sq](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ess3sq/32/26834_2.png) [@ess3sq](https://discourse.julialang.org/u/ess3sq)\
**Post date:** [July 5, 2021, 1:16pm UTC](https://discourse.julialang.org/t/repl-in-vs-code-stalling-overnight/63976/8 "2021-07-05T13:16:49Z")

</div>

For me (Juno REPL panel) it freezes randomly while nothing is being executed (REPL idle) and the Atom window is active (as in I’m doing stuff in it).

Again, not sure if this is relevant to the VS Code issue described in the OP, but it sounds similar.