Frequent crashes (10-30) daily with no discernible pattern

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.

VS Version:

Extensions:

Powershell Version:

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!

[carsontwilson]

The logs don’t seem to show much, but I’ve included a zip file with all logging information - I just had two such crashes in a row. Many of the log files are 0kb with no data, but there are a couple with sparse info.

Let me know if I can do more or if there’s more logging elsewhere I can include (this is coming from: C:\Users\CarsonWilson\AppData\Roaming\Code\logs)

20190823T093944.zip

Edit: Ugh my bad I was at normal logging, I’ve changed to verbose - let’s see what it turns up! 😃

[msftbot[bot]]

This issue was closed automatically as repro info was indicated as needed, but there has been no activity in over a week. Please feel free to reopen with any available information!