Interactive Console Stops Responding

[adamdriscoll]

System Details

System Details Output

### VSCode version: 1.42.1 c47d83b293181d9be64f27ff093689e8e7aed054 x64

### VSCode extensions:
eamodio.gitlens@10.2.1
Equinusocio.vsc-community-material-theme@1.4.1
Equinusocio.vsc-material-theme@32.5.0
equinusocio.vsc-material-theme-icons@1.1.4
johnpapa.vscode-peacock@3.5.0
ms-dotnettools.csharp@1.21.13
ms-vscode.powershell@2020.3.0
ms-vsliveshare.vsliveshare@1.0.1711
ms-vsliveshare.vsliveshare-audio@0.1.80
ms-vsliveshare.vsliveshare-pack@0.3.4
vscode-icons-team.vscode-icons@10.0.0
wix.vscode-import-cost@2.12.0


### PSES version: 2.0.0.0

### PowerShell version:

Name                           Value
----                           -----
PSVersion                      5.1.18362.628
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.18362.628
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Issue Description

The PowerShell Interactive Console no longer accepts keystrokes sometimes. It's very hit or miss but has happened to me a couple of times today.

Expected Behaviour

The interactive console continues to function.

Actual Behaviour

Typing doesn't have any effect on the interactive console.

https://recordit.co/Ral9dac8RT

Attached Logs

Follow the instructions in the troubleshooting docs
about capturing and sending logs.

[rkeithhill]

This has happened to me too on 2020.3.0.

[TylerLeonhardt]

Have either of you been using the Preview extension? Curious if you ever saw that behavior then.

You could still try the PowerShell Preview extension which is currently slightly behind Stable...

I want to try and narrow down when this problem started happening.

[adamdriscoll]

I wasn't using the preview extension day-to-day. I installed it a couple of times but ran into issues so I was on the previous stable. So this is the first I'm seeing this behavior.

I can try the preview to see if I see it there.

[adamdriscoll]

I just ran into this again. This time, I realized something was wrong when I couldn't start the debugger. The terminal is also stuck. Here's my log. I have diagnostic logging enabled but I don't see any diagnostic level stuff so I'm not sure what's up with that.

3/7/2020 8:34:03 AM [NORMAL] - Visual Studio Code v1.42.1 64-bit
3/7/2020 8:34:03 AM [NORMAL] - PowerShell Extension v2020.3.0
3/7/2020 8:34:03 AM [NORMAL] - Operating System: Windows 64-bit
3/7/2020 8:34:03 AM [NORMAL] - Language server starting --
3/7/2020 8:34:03 AM [NORMAL] -     PowerShell executable: C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
3/7/2020 8:34:03 AM [NORMAL] -     PowerShell args: -NoProfile -NonInteractive -ExecutionPolicy Bypass -Command Import-Module 'c:\Users\adamr\.vscode\extensions\ms-vscode.powershell-2020.3.0\modules\PowerShellEditorServices\PowerShellEditorServices.psd1'; Start-EditorServices -HostName 'Visual Studio Code Host' -HostProfileId 'Microsoft.VSCode' -HostVersion '2020.3.0' -AdditionalModules @('PowerShellEditorServices.VSCode') -BundledModulesPath 'c:\Users\adamr\.vscode\extensions\ms-vscode.powershell-2020.3.0\modules' -EnableConsoleRepl -LogLevel 'Diagnostic' -LogPath 'c:\Users\adamr\.vscode\extensions\ms-vscode.powershell-2020.3.0\logs\1583595243-bfa2bad5-5c6f-4411-99a2-3754bd34d4c01583595231974\EditorServices.log' -SessionDetailsPath 'c:\Users\adamr\.vscode\extensions\ms-vscode.powershell-2020.3.0\sessions\PSES-VSCode-19380-591224' -FeatureFlags @() 
3/7/2020 8:34:03 AM [NORMAL] -     PowerShell Editor Services args: Import-Module 'c:\Users\adamr\.vscode\extensions\ms-vscode.powershell-2020.3.0\modules\PowerShellEditorServices\PowerShellEditorServices.psd1'; Start-EditorServices -HostName 'Visual Studio Code Host' -HostProfileId 'Microsoft.VSCode' -HostVersion '2020.3.0' -AdditionalModules @('PowerShellEditorServices.VSCode') -BundledModulesPath 'c:\Users\adamr\.vscode\extensions\ms-vscode.powershell-2020.3.0\modules' -EnableConsoleRepl -LogLevel 'Diagnostic' -LogPath 'c:\Users\adamr\.vscode\extensions\ms-vscode.powershell-2020.3.0\logs\1583595243-bfa2bad5-5c6f-4411-99a2-3754bd34d4c01583595231974\EditorServices.log' -SessionDetailsPath 'c:\Users\adamr\.vscode\extensions\ms-vscode.powershell-2020.3.0\sessions\PSES-VSCode-19380-591224' -FeatureFlags @() 
3/7/2020 8:34:03 AM [NORMAL] - powershell.exe started.
3/7/2020 8:34:03 AM [NORMAL] - Waiting for session file
3/7/2020 8:34:07 AM [NORMAL] - Session file found
3/7/2020 8:34:07 AM [NORMAL] - Registering terminal close callback
3/7/2020 8:34:07 AM [NORMAL] - Registering terminal PID log callback
3/7/2020 8:34:07 AM [NORMAL] - powershell.exe PID: 23240
3/7/2020 8:34:07 AM [NORMAL] - Language server started.
3/7/2020 8:34:07 AM [NORMAL] - {"status":"started","languageServiceTransport":"NamedPipe","languageServicePipeName":"\\\\.\\pipe\\PSES_0v4lvglr.tej","debugServiceTransport":"NamedPipe","debugServicePipeName":"\\\\.\\pipe\\PSES_eosq4etr.e3y"}
3/7/2020 8:34:07 AM [NORMAL] - Connecting to language service on pipe \\.\pipe\PSES_0v4lvglr.tej...
3/7/2020 8:34:07 AM [NORMAL] - Language service connected.
3/7/2020 8:34:10 AM [WARNING] - Invalid Version: null

The last warning there was like 15 minutes before I actually encountered the problem.

[adamdriscoll]

Here's the editor service log.

log.txt

[rjmholt]

@adamdriscoll what PackageManagement version do you have installed? Can you try updating it past 1.4.5 and see if this continues?

[adamdriscoll]

I have 1.4.6 installed (with a bunch of others, apparently)

PS F:\universal-automation\src\installer> get-module packagemanagement -list



    Directory: C:\Users\adamr\Documents\WindowsPowerShell\Modules


ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     1.4.6      PackageManagement                   {Find-Package, Get-Package, Get-PackageProvider, Get-PackageSource...}
Script     1.3.1      PackageManagement                   {Find-Package, Get-Package, Get-PackageProvider, Get-PackageSource...}
Script     1.1.7.2    PackageManagement                   {Find-Package, Get-Package, Get-PackageProvider, Get-PackageSource...}


    Directory: C:\Program Files\WindowsPowerShell\Modules


ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     1.2.4      PackageManagement                   {Find-Package, Get-Package, Get-PackageProvider, Get-PackageSource...}
Script     1.2.3      PackageManagement                   {Find-Package, Get-Package, Get-PackageProvider, Get-PackageSource...}
Script     1.1.7.0    PackageManagement                   {Find-Package, Get-Package, Get-PackageProvider, Get-PackageSource...}
Binary     1.0.0.1    PackageManagement                   {Find-Package, Get-Package, Get-PackageProvider, Get-PackageSource...}

[rjmholt]

If you run import-module PackageManagement -passthru in the integrated console it should tell you which is being used there

[adamdriscoll]

It's using 1.4.6

import-module PackageManagement -passthru


ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     1.4.6      PackageManagement                   {Find-Package, Find-PackageProvider, Get-Package, Get-PackageProvider...}

[bvbeek]

Same issue here with version 1.0.0.1 of PackageManagement
Several days the console is unusable and F8 and F5 also not working. Need to reload window.

import-module PackageManagement -passthru

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Binary     1.0.0.1    PackageManagement                   {Find-Package, Find-PackageProvider, Get-Package, Get-PackageProvider...}

[rjmholt]

Same issue here with version 1.0.0.1 of PackageManagement

@bvbeek you'll need to upgrade PackageManagement. Older versions of it have an issue that cause deadlocks when working in PSES. We spent some time looking into it and it wasn't possible to mitigate from PSES; instead @SeeminglyScience fixed the underlying issue in PackageManagement.

Beyond that though it does sound like there's another issue in the extension somewhere, but we haven't been able to reproduce it yet or collect enough information to have an inkling of why it's occurring.