-
Notifications
You must be signed in to change notification settings - Fork 523
Description
While attempting to debug VS Code using the powershell console, the console itself will crash many, many times per day.
The behaviour is always the same, but I can't determine why it happens or see any pattern. When it does happen, it's always when you first start debugging, console just sits there as if frozen.
After a few moments, VS will alert me of an issue with the window, ask me to re-open or wait. Waiting doesn't seem to be helpful (though I've not waited for more than 5 minutes). Re-opening the window will basically restart VS Code and I can typically proceed from there.
I can mitigate this, somewhat, if I "trash" all console instances before I start (i.e. hit the little garbage can on the bottom of the console essentially restarting it), though that doesn't always work either.
Logs:
vscode-powershell.log
EditorServices.log
DebugSession-1.log
In this case, I consistently see this error across multiple sessions:
2019-07-29 16:53:25.033 [ERROR] tid:15 in 'ExecuteCommand' C:\PowerShellEditorServices\src\PowerShellEditorServices\Session\PowerShellContext.cs: line 565
Execution of the following command(s) completed with errors:
c:\Work\devops\powershell\test.ps1
Out-Default
There are days when my extension can crash 30+ times which is challenging to say the least.
I've completely uninstalled / reinstalled the extension, VS Code etc. but the results remain the same.
One thing that may or may not be worth noting, in that script (and all my scripts basically) I reference multiple powershell classes as well, that are being imported like this:
using module .\modules\EnvironmentData.psm1
using module .\modules\Tenant.psm1
using module .\modules\ADManager.psm1
using module .\modules\AzureFunction.psm1
Thanks!


