Second program startup produces wall of text

[niwax]

Environment data

• VS Code version: 14.0.1 (user setup)
• Extension version (available under the Extensions sidebar): 2019.10.44104
• OS and version: Windows 10.0.18362.418
• Python version (& distribution if applicable, e.g. Anaconda): 3.6.7 x64
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
• Relevant/affected Python packages and their versions: N/A
• Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info How to update the language server to the latest stable version #3977): Jedi

Expected behaviour

When using Debug > Start Debugging or Debug > Start Without Debugging, the program should start in a timely manner and write its output to the console.

Actual behaviour

Starting from the second use of each function, VS code produces a wall of text on the console for several seconds before the program starts. The users PowerShell console history outside of VS Code is also spammed with the messages.

This happens for either start option independently, the first execution of both works as expected.

Steps to reproduce:

1. Start the program through Debug > Start Debugging or Debug > Start Without Debugging
2. Wait for the program to finish
3. Start another debugging session through the same method as 1.

(optional) Open a PowerShell independently of VS Code and press the up arrow to cycle through the messages.

Logs

The Output console shows nothing beyond a suggestion to install pylint.

I have uploaded the offending output from Terminal > Python Debug Console here for brevity: https://gist.github.com/niwax/e42c80ff9bbe104a4a86e2554fa95bea

[karrtikr]

The issue seems to be a dup of #7436

Please try some of the workarounds mentioned there,

• close the Python debug console every time you are done debugging (so that it re-creates a terminal next time)
• use a different shell (git bash, cmd, another version of powershell-core or Windows Powershell)

[karrtikr]

We'll look into a more permanent soln of this issue when working on #8180.

[karrtikr]

Closing in favor of #8180 for now.

[karthiknadig]

See #8820 for the fix and #8180 (comment) for the explanation.

[karrtikr]

Validated✅