Large number of creation powershell.exe processes

[Tovey]

Environment data

• VS Code version: 1.28.2
• Extension version (available under the Extensions sidebar): 2018.9.0
• OS and version: windows 7, 64bit
• Python version (& distribution if applicable, e.g. Anaconda): Python 3.7.0
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
• Relevant/affected Python packages and their versions: XXX

Actual behavior

I was run python command in VSCode Terminal, with matplotlib.pyplot to draw picture, but after a while, a lot of powershell.exe processes were created in Windows task manager, and resulting in insufficient memory.
This problem was disappeared when disabled this extension.

Expected behavior

No powershell.exe process resides in Windows task manager

Steps to reproduce:

1. run python scipt with matplotlib.pyplot in VSCode Terminal or F5;
2. run sometimes then see windows task manager.

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

Starting Jedi Python language engine.
##########Linting Output - flake8##########
##########Linting Output - pylint##########
************* Module gps_label_split_by_time
12,14,warning,W0612:Unused variable 'dir_names'
18,20,warning,W0612:Unused variable 'line'

------------------------------------------------------------------

Your code has been rated at 9.64/10 (previous run: 9.64/10, +0.00)



##########Linting Output - flake8##########
5,1,F,F401:'matplotlib.lines.Line2D' imported but unused
12,18,W,W291:trailing whitespace
20,5,E,E266:too many leading '#' for block comment
##########Linting Output - pylint##########
************* Module plot_gps_satellite
6,0,error,E0611:No name 'ConvexHull' in module 'scipy.spatial'

------------------------------------------------------------------

Your code has been rated at 8.86/10 (previous run: 8.86/10, +0.00)



##########Linting Output - flake8##########
##########Linting Output - pylint##########

--------------------------------------------------------------------

Your code has been rated at 10.00/10 (previous run: 10.00/10, +0.00)

Output for Log(Extension Host) in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Log(Extension Host))

[2018-10-18 16:53:34.391] [exthost] [info] extension host started
[2018-10-18 16:53:34.407] [exthost] [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch {"startup":true,"activationEvent":"*"}
[2018-10-18 16:53:34.407] [exthost] [info] ExtensionService#loadCommonJSModule d:\program\Microsoft VS Code\resources\app\extensions\debug-auto-launch\dist\extension
[2018-10-18 16:53:34.412] [exthost] [info] ExtensionService#_doActivateExtension vscode.emmet {"startup":true,"activationEvent":"*"}
[2018-10-18 16:53:34.412] [exthost] [info] ExtensionService#loadCommonJSModule d:\program\Microsoft VS Code\resources\app\extensions\emmet\dist\extension
[2018-10-18 16:53:34.445] [exthost] [info] ExtensionService#_doActivateExtension vscode.git {"startup":true,"activationEvent":"*"}
[2018-10-18 16:53:34.445] [exthost] [info] ExtensionService#loadCommonJSModule d:\program\Microsoft VS Code\resources\app\extensions\git\dist\main
[2018-10-18 16:53:34.558] [exthost] [info] ExtensionService#_doActivateExtension vscode.merge-conflict {"startup":true,"activationEvent":"*"}
[2018-10-18 16:53:34.558] [exthost] [info] ExtensionService#loadCommonJSModule d:\program\Microsoft VS Code\resources\app\extensions\merge-conflict\dist\extension
[2018-10-18 16:53:34.564] [exthost] [info] ExtensionService#_doActivateExtension vscode.search-rg {"startup":true,"activationEvent":"*"}
[2018-10-18 16:53:34.564] [exthost] [info] ExtensionService#loadCommonJSModule d:\program\Microsoft VS Code\resources\app\extensions\search-rg\dist\extension
[2018-10-18 16:53:34.568] [exthost] [info] eager extensions activated
[2018-10-18 16:53:34.571] [exthost] [info] ExtensionService#_doActivateExtension vscode.python {"startup":false,"activationEvent":"onLanguage:python"}
[2018-10-18 16:53:34.571] [exthost] [info] ExtensionService#loadCommonJSModule d:\program\Microsoft VS Code\resources\app\extensions\python\out\pythonMain
[2018-10-18 16:55:42.256] [exthost] [info] extension host started
[2018-10-18 16:55:42.273] [exthost] [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch {"startup":true,"activationEvent":"*"}
[2018-10-18 16:55:42.273] [exthost] [info] ExtensionService#loadCommonJSModule d:\program\Microsoft VS Code\resources\app\extensions\debug-auto-launch\dist\extension
[2018-10-18 16:55:42.280] [exthost] [info] ExtensionService#_doActivateExtension vscode.emmet {"startup":true,"activationEvent":"*"}
[2018-10-18 16:55:42.280] [exthost] [info] ExtensionService#loadCommonJSModule d:\program\Microsoft VS Code\resources\app\extensions\emmet\dist\extension
[2018-10-18 16:55:42.313] [exthost] [info] ExtensionService#_doActivateExtension vscode.git {"startup":true,"activationEvent":"*"}
[2018-10-18 16:55:42.313] [exthost] [info] ExtensionService#loadCommonJSModule d:\program\Microsoft VS Code\resources\app\extensions\git\dist\main
[2018-10-18 16:55:42.431] [exthost] [info] ExtensionService#_doActivateExtension vscode.merge-conflict {"startup":true,"activationEvent":"*"}
[2018-10-18 16:55:42.431] [exthost] [info] ExtensionService#loadCommonJSModule d:\program\Microsoft VS Code\resources\app\extensions\merge-conflict\dist\extension
[2018-10-18 16:55:42.439] [exthost] [info] ExtensionService#_doActivateExtension vscode.search-rg {"startup":true,"activationEvent":"*"}
[2018-10-18 16:55:42.439] [exthost] [info] ExtensionService#loadCommonJSModule d:\program\Microsoft VS Code\resources\app\extensions\search-rg\dist\extension
[2018-10-18 16:55:42.443] [exthost] [info] eager extensions activated
[2018-10-18 16:55:42.446] [exthost] [info] ExtensionService#_doActivateExtension vscode.python {"startup":false,"activationEvent":"onLanguage:python"}
[2018-10-18 16:55:42.446] [exthost] [info] ExtensionService#loadCommonJSModule d:\program\Microsoft VS Code\resources\app\extensions\python\out\pythonMain
[2018-10-18 16:55:42.447] [exthost] [info] ExtensionService#_doActivateExtension ms-python.python {"startup":false,"activationEvent":"onLanguage:python"}
[2018-10-18 16:55:42.447] [exthost] [info] ExtensionService#loadCommonJSModule C:\Users\Administrator\.vscode\extensions\ms-python.python-2018.9.0\out\client\extension

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)

![console_output](https://user-images.githubusercontent.com/8827460/47144128-57692b80-d2f9-11e8-842e-252c31907abf.png)

Other pictures

[DonJayamanne]

• Can you disable the extension and run the command py -3 test.py and check whether the powershell.exe process is still created?

The Python Extension doesn't launch the powershell.exe process at all, the only way it can get launched is via the terminal, and that's done by VS Code itself, and not the extension.

[Tovey]

disabled this extension, the powershell.exe process will not create, see figure1,

but when open this extension and run test.py by press F5 many times，the powershell.exe will be created more and more, see figure2.

[DonJayamanne]

Please could you uninstall the extension and try the following repeatedly"
cd F:\AR_IO & cmd /C "set "PYTHONIOENCODING=UTF-8" && D:\Program\...python.exe F:\AR_IO\test.py "

Basically execute the same command but only pass the file name test.py as an argument to the python executable.

I believe the problem is with the terminal in vsc.

Please try running the above in the terminal repeatedly (copy paste paste paste paste...)..

[Tovey]

I run the script but the results did not meet your expectations.

figure1: installed extension, but run command without extension, create 1 powershell.exe process.

figure2: installed extension, run command with extension(used by F5), create many powershell.exe process.

figure3: uninstall extension, run command without extension, create 0 powershell.exe process.

[DonJayamanne]

figure2: installed extension, run command with extension(used by F5), create many powershell.exe process.

Looking at the screen sample, there's only one powershell.exe!

[DonJayamanne]

Also, please could you ensure you have updated the extension to the latest version (todays release).

[Tovey]

figure2: There were three powershell.exe at this time(10:53:16).
the extension's version is 2018.9.1.