Lots of jedi subprocesses created until memory runs out

It seems to be a regression of https://github.com/microsoft/vscode-python/issues/3586 and https://github.com/microsoft/vscode-python/issues/3514 . This started to happen recently (I can’t tell exactly when, but a couple of weeks back I didn’t experience this issue).

Environment data

• VS Code version: 1.37.1
• Extension version (available under the Extensions sidebar): 2019.8.30787
• OS and version: MacOS High Sierra Version 10.13.6
• Python version (& distribution if applicable, e.g. Anaconda): Python 3.7.3
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): virtualenv
• Relevant/affected Python packages and their versions: XXX
• Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): Jedi

Actual behaviour

After working for a while in a Django project, python completion.py spawns lots of subprocesses that are never killed. Eventually the system runs out of memory and fork fails. You can close the visual studio folder in order to free memory, but it takes a while for the python processes to be killed and the computer gets unresponsive.

Steps to reproduce:

1. Open a python project
2. Browse some files, and on each of them call autocomplete and save several times. After a while you should get a lot processes that won’t go away.

[deitry]

Hi. There is also similar problem for pylint: https://github.com/microsoft/vscode-python/issues/4236 I found recently that processes do not die automatically when spawned for files with errors. Maybe there is something common in these issues?

[DonJayamanne]

@deitry Thanks, however that’s a separate issue even though they may seem related. We’ll monitor/track that issue separately. If indeed they end up being related (generic issue), then we’ll end up fixing this as well.