vscode-powershell: F5 stops working after being idle for hours

Prerequisites

  • I have written a descriptive issue title.
  • I have searched all issues to ensure it has not already been reported.
  • I have read the troubleshooting guide.
  • I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
  • I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
  • If this is a security issue, I have read the security issue reporting guidance.

Summary

I was using VSCode happily and left it idling overnight. When I came back in the morning pressing F5 no longer worked. It shows “debugging” started but nothing actually happens.

1653152189-b24c1707-c9d4-4dd2-bd79-c3b812fa2ef31653152188112.zip

After restarting the session - things work again. I’ve seen it before in earlier previews.

PowerShell Version

Name                           Value
----                           -----
PSVersion                      7.3.0-preview.3
PSEdition                      Core
GitCommitId                    7.3.0-preview.3
OS                             Microsoft Windows 10.0.22000
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visual Studio Code Version

1.67.2                                                                                                                                                                                                                                                                                                        
c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5                                                                                                                                                                                                                                                                      
x64

Extension Version

ms-vscode.powershell@2022.5.1
ms-vscode.powershell-preview@2022.5.5                                                                                                                                                                                                                                                                         
tobysmith568.run-in-powershell@1.1.1                                                                                                                                                                                                                                                                          
TylerLeonhardt.vscode-inline-values-powershell@0.0.5

Steps to Reproduce

Hard to say if it’s just being idle or something else is in play.

Visuals

No response

Logs

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 17 (10 by maintainers)

Most upvoted comments

Have successfully tested with 2022.5.1 and the issue is not present

I actually started having this issue more and more 😦

Haven’t noticed really. Probably yes. If it happens again I will report. For me it happens very rarely and I can’t really complain.

I have two machine and one is working perfectly with no issue I suspect a module to be the problem root cause will remove them one by one until I find the suspect

Haven’t noticed really. Probably yes. If it happens again I will report. For me it happens very rarely and I can’t really complain.