Extension/Integrated Console hangs on startup before prompt

[metalmensch]

Issue Type: Bug

Open Visual Studio Code (the terminal window won't load after five minutes with 30 gb of RAM).

Extension version: 2019.5.0
VS Code version: Code 1.35.0 (553cfb2c2205db5f15f3ee8395bbd5cf066d357d, 2019-06-04T01:17:12.481Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz (4 x 2808)
GPU Status	2d_canvas: disabled_software checker_imaging: disabled_off flash_3d: disabled_software flash_stage3d: disabled_software flash_stage3d_baseline: disabled_software gpu_compositing: disabled_software multiple_raster_threads: disabled_off native_gpu_memory_buffers: disabled_software rasterization: disabled_software surface_synchronization: disabled_off video_decode: disabled_software webgl: disabled_off webgl2: disabled_off
Load (avg)	undefined
Memory (System)	23.87GB (12.35GB free)
Process Argv
Screen Reader	no
VM	0%

[MarkKharitonov]

I second this motion. Was about to open an issue myself. The console window just shows PowerShell Integrated Console and that's it.

[rjmholt]

Thanks for opening an issue. If we can find a way to reproduce it, we can hopefully fix it.

the terminal window won't load after five minutes with 30 gb of RAM

This is likely not a performance issue.

A couple of questions:

• If you go to the Integrated Console and press Enter, does it then continue?
• When did this last work for you? Did it stop working when VSCode (not the extension) updated? Or when the PowerShell extension updated at the end of May?
• In @metalmensch's case, does it display anything in the terminal? Do you have a PowerShell file open?
• In @MarkKharitonov's case, what operating system (and version) are you running?
• If you try to restart the PowerShell extension session (with Ctrl+Shift+P PowerShell: Restart Current Session), what happens?
• If you open a native powershell or pwsh terminal, does a similar problem occur?

We're aware of a Windows bug that's been affecting recent VSCode builds in which the terminal doesn't behave properly, so that's my current suspicion.

[rjmholt]

See also: #1795 (comment)

[metalmensch]

It looks like it was being stopped by a pending windows update on my end. I rebooted, and it seems to have gone back to working.

…

On Thu, Jun 6, 2019 at 1:24 PM Robert Holt ***@***.***> wrote: One test is: if you go to an ordinary native powershell terminal, does something similar happen? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2014?email_source=notifications&email_token=AGUA7HPI6VOVBAHPXJ6CUATPZFW75A5CNFSM4HVICWCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXEBWAY#issuecomment-499653379>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGUA7HNSFF5GREBENDQTSZ3PZFW75ANCNFSM4HVICWCA> .

[MarkKharitonov]

I would like to answer the questions:

• If you go to the Integrated Console and press Enter, does it then continue?

No, still stuck at PowerShell Integrated Console

• When did this last work for you? Did it stop working when VSCode (not the extension) updated? Or when the PowerShell extension updated at the end of May?

Sorry, but I do not know.

• In @MarkKharitonov's case, what operating system (and version) are you running?

I have two machines. On the "good" the Powershell console opens OK., On the "bad" - it is stuck. In both cases it is Windows 10.
Here is the info:
"Bad" Machine
Powershell Integrated Console hangs, pressing Enter does not help. At least not in the first N minutes, where N is sizeable (10?)
VS Code

Version: 1.34.0 (system setup)
Commit: a622c65b2c713c890fcf4fbf07cf34049d5fe758
Date: 2019-05-15T21:59:37.030Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763

Powershell extension

Name: PowerShell
Id: ms-vscode.powershell
Description: Develop PowerShell scripts in Visual Studio Code!
Version: 2019.5.0
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-vscode.PowerShell

"Good" Machine
VS Code

Version: 1.34.0 (system setup)
Commit: a622c65b2c713c890fcf4fbf07cf34049d5fe758
Date: 2019-05-15T21:59:37.030Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.16299

Powershell extension

Name: PowerShell
Id: ms-vscode.powershell
Description: Develop PowerShell scripts in Visual Studio Code!
Version: 2019.5.0
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-vscode.PowerShell

• If you try to restart the PowerShell extension session (with Ctrl+Shift+P PowerShell: Restart Current Session), what happens?

Same thing - it hangs.

• If you open a native powershell or pwsh terminal, does a similar problem occur?

No.

[rjmholt]

Hmmm it certainly looks like the only difference between machines is the Windows version (which implies it may be the Windows bug).

Another thing it might be worth doing is turning the logging up to Diagnostic and seeing how far you get through startup

[MarkKharitonov]

Actually on the "bad" machine hitting many times Enter does force the console to show the prompt. So, yes - hitting multiple times Enter shows the console. But, it does not load the profile.

I will get the logs later.

[rjmholt]

hitting multiple times Enter shows the console

Yeah that sounds like the relevant Windows bug.

But, it does not load the profile

Which profile is that? The PowerShell extension looks for the profile in ~\Documents\PowerShell\Microsoft.VSCode_profile.ps1. I assume this works on the good machine?

[MarkKharitonov]

Yes, it does not load the $PROFILE, whatever it should be in this context. Does load on the "good" machine.

Note that once the prompt is shown explicitly loading $PROFILE works fine.

[rjmholt]

Note that once the prompt is shown explicitly loading $PROFILE works fine.

Ohhhh, as in it loads once you press Enter?

Yeah that's because this Windows bug just stops the startup from proceeding (it's a bug in the Windows console APIs), before it can get to the profile execution stage. It's like if you put Wait-Debugger at the start of your profile.

The fix lies below the extension -- it's something we depend on VSCode and Windows for. From what I can tell, the fix is to run Windows update.