You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Extension causes high cpu load due to interpreter discovery #11924
All these cases are due to how the extension tries to find and figure out the details about the interpreter. We are in the process of refactoring the code that does interpreter discovery. One of the thing we are making sure is to reduce the number of python processes we create while figuring out interpreter info.
Extension removed support for opting out of pythonDiscoveryModuleWithoutWatcher with 2021.10.1317843341 (see #17563), which is why it started happening now for you guys. But it seems the new discovery code (meaning experiment pythonDiscoveryModuleWithoutWatcher) was likely buggy going way back.
Kartik Raj (@karrtikr) Version v2021.9.1246542782 also works for me. I tried it based on sn0wfa11's earlier post: #11924 (comment)
I do not have any opt outs in my settings (see my settings_json.txt file above). Also, note that python.logging.level and files.watcherExclude were only added for this testing; those are not typically there for my settings.
Just updated to 1.61.0 and this crap started again... The opt-outs are already in place. It gets stuck on "Discovering Python Interpreters". Trying to use the circuitpython extension. ms-python.python-unresponsive.cpuprofile.txt
It looks like the extension cannot find an interpreter when selecting "open folder" and opening the microcontroller drive. If I copy the files off to a non-external drive it works fine...
Create a new folder in D:\ drive not in D:\ and it worked well !
Activity
shyamyadati commentedon May 22, 2020
I can also confirm the same issue on OS X:
microsoft/vscode#98286 (comment)
karthiknadig commentedon May 26, 2020
condor (@connerf) Can you please attach the
cpu-profile.txtfrom hereC:\Users\cferguson\ms-python.python-unresponsive.cpuprofile.txtconnerf commentedon May 26, 2020
Karthik Nadig (@karthiknadig) is this what you are looking for? Or would you prefer the text in this box?
ms-python.python-unresponsive.cpuprofile.txt
ParthiBa commentedon Jul 12, 2020
ms-python.python-unresponsive.cpuprofile.txt
it very slow while changing python interpreter . if i am using non -venv or non-pyenv then is not an issue
coreysharris commentedon Jul 15, 2020
ms-python.python-unresponsive.cpuprofile.txt
karthiknadig commentedon Jul 15, 2020
All these cases are due to how the extension tries to find and figure out the details about the interpreter. We are in the process of refactoring the code that does interpreter discovery. One of the thing we are making sure is to reduce the number of python processes we create while figuring out interpreter info.
73 remaining items
karrtikr commentedon Oct 15, 2021
Very interesting, thank you. Just having
works for me.
Extension removed support for opting out of
pythonDiscoveryModuleWithoutWatcherwith2021.10.1317843341(see #17563), which is why it started happening now for you guys. But it seems the new discovery code (meaning experimentpythonDiscoveryModuleWithoutWatcher) was likely buggy going way back.I'll let you know if I need anything else.
mpratscher commentedon Oct 16, 2021
Kartik Raj (@karrtikr) Version
v2021.9.1246542782also works for me. I tried it based on sn0wfa11's earlier post: #11924 (comment)I do not have any opt outs in my settings (see my settings_json.txt file above). Also, note that
python.logging.levelandfiles.watcherExcludewere only added for this testing; those are not typically there for my settings.karrtikr commentedon Oct 16, 2021
mpratscher Noted, thanks.
You actually have telemetry disabled, which effectively means you have opted out of all experiments.
Touyu-Pan commentedon Oct 16, 2021
I'm getting stuck at "Discovering Python Interpreters".
I really could use some helps
ms-python.python-unresponsive.cpuprofile.txt
Python output.txt
settings_json.txt
.
iScottMark commentedon Oct 18, 2021
Create a new folder in D:\ drive not in D:\ and it worked well !
[-]Extension causes high cpu load[/-][+]Extension causes high cpu load due to interpreter discovery[/+]karrtikr commentedon Oct 18, 2021
Should be fixed with #17781. Use
Extension: Install from VSIXcommand to install the following VSIX: https://github.com/microsoft/vscode-python/suites/4087722570/artifacts/104116878 which has the fix!Touyu-Pan commentedon Oct 19, 2021
Lots of thanks!!!
jing-bi commentedon Nov 5, 2021
Seems the VSIX is expired, can you please repost it again?
karthiknadig commentedon Nov 5, 2021
Jing Bi (@jing-bi) This is now released, you can find the VSIX here https://github.com/microsoft/vscode-python/releases/download/2021.11.1422169775/ms-python-release.vsix