forked from DonJayamanne/pythonVSCode
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buginfo-neededIssue requires more information from posterIssue requires more information from poster
Description
Environment data
- VS Code version: 1.42.1 (also seen with 1.42, 1.41.1)
- Extension version (available under the Extensions sidebar): 2020.2.64397
- OS and version: Mac Catalina
- Python version (& distribution if applicable, e.g. Anaconda): 3.6.4
- Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
Expected behaviour
I can use the plugin and any Python processes that get spawned use a modest amount of CPU and exit when done. My tests take about 1 minute.
Actual behaviour
Using this extension causes Python processes using high CPU to get spawned and stick around until I force quit them. The more VS Code tabs I open, the more processes get spawned. Tests take 5x as long.
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
- With the plugin installed, open several tabs of Python code. Test and lint as normal.
- Observe the activity monitor.
jorgii
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buginfo-neededIssue requires more information from posterIssue requires more information from poster