forked from DonJayamanne/pythonVSCode
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Labels
area-lintingbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugneeds proposalNeed to make some design decisionsNeed to make some design decisions
Description
Environment data
- VS Code version: 1.30.2
- Extension version (available under the Extensions sidebar): 2019.1.0
- OS and version: Linux Mint 19.1
- Python version (& distribution if applicable, e.g. Anaconda): 3.6.7
- Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv
- Relevant/affected Python packages and their versions: pylint 2.2.2
Expected behaviour
To only have one python process running pylint for each file open.
Actual behaviour
Hundreds of pylint processes open.
Steps to reproduce:
Not exactly sure, only noticed when computer started swapping to disk and check memory usage, but general steps to start having the processes spawn.
- Open and close python files.
- Enable pylint.
More python processes running pylint will open as time goes on and files get closed/opened. The processes don't end when the file is closed.
Barrot, RDReavis, SamyCookie, Nolent, jeffgabhart and 12 moresamuela
Metadata
Metadata
Assignees
Labels
area-lintingbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugneeds proposalNeed to make some design decisionsNeed to make some design decisions