-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension is launching far too many processes and not closing them correctly #3608
Comments
Also, all of these Python processes show the same command line: So it's pretty clear that this extension is the cause. |
I seem to have been experiencing this as well. I think after the last extension update. And it is bad enough that over time it will spawn enough processes that my system will stop being able to fork new processes (not entirely sure what limit is exhausted. As I seem to still be able to open applications) For me I am fairly sure it is the selected python in my project though. Which in the case is 2.7 though a virtualenv |
From a quick observation it seems highly likely to be related to the machine sleeping. All morning I have had two processes. Coming back from lunch and waking my machine I now have 11. |
It could also be an issue with Jedi (davidhalter/jedi#1242) itself. Perhaps the extension upgraded to a problematic version? |
This also happens to me on macOS 10.14.1. Same VS Code, extension, and Python versions. But with pipenv's virtualenv. |
Seems like the same issue as #3514 |
You are right @frizz925 . Somehow I missed that one |
Duplicate of #3514 |
Environment data
python -VV
output:Expected behaviour
Opening an editor for a Python file in VSCode launches a Python process to run the extension for that editor. Closing the editor terminates the associated Python process, so that the number of Python processes is equal to the number of Python file editors currently open.
Actual behaviour
Opening an editor for a Python file in VSCode launches a Python process to run the extension for that editor. Closing the editor does NOT terminate the associated Python process, leaving it running forever unless either VSCode is closed completely or the process is manually killed via the operating system. As long as VSCode remains open, the number of Python processes grows without upper bound as Python editors are opened, slowly consuming large amounts of memory in a manner very similar to a fork bomb and pushing other processes into swap, which eventually brings the entire operating system to a halt. I had over 5 GiB of stuff in swap by the time I realized what was happening, and it took 5 to 10 minutes for the computer to respond to my attempts to close programs.
Steps to reproduce:
Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
)(Annotation: The "python3.3" interpreter referenced above is NOT the one running the extension, or one that I use in any way. It is an old one that I intend to delete when I have some time to clean things up.)
The text was updated successfully, but these errors were encountered: