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
⚠️ Make sure to attach this file from your home-directory: ⚠️file:///c%3A/Users/Concreta/AppData/Local/Temp/ms-python.python-unresponsive.cpuprofile.txt
I'm experiencing this issue as well. Upon launching the editor, everything runs normally as long as I don't open any Python files. However, the moment I open one and the editor starts loading plugin services, my CPU usage spikes to near 100%.
The Python Language Server plugin works for a brief moment (about a minute), but then it gets interfered with by this specific plugin and stops functioning. This results in persistent high background CPU usage. I've tried different versions of the plugin, but the issue persists, so it doesn't seem to be version-specific. I suspect it might be caused by a recent VS Code update breaking compatibility.
After multiple attempts of closing and reopening the editor, it suddenly worked normally once, but closing and reopening it again reverted it back to the high CPU usage state. During this state, rendering becomes laggy. While syntax highlighting still works, features like comment hints, code completion (IntelliSense), go-to-definition, and code suggestions all fail. There is also about a one-second delay when pressing Enter.
After troubleshooting, I've ruled out conflicts with other extensions; this is definitely caused by the plugin itself.
Python Environments output channel (important since discovery is managed by this extension)
[optional] Test without Pylance: Does the high CPU issue occur if you disable the Pylance extension? This would help us determine if the issue is in Python, Python Environments, or Pylance.
[optional] Extension list: Please share your installed extensions (code --list-extensions).
@xihusuli — I noticed your logs show a working session (Pylance starting successfully). Could you capture the logs during the high CPU/non-responsive state?
Eleanor Boyd (@eleanorjboyd)
There is good news—that it might be an issue with VS Code itself; after a small VS Code update yesterday afternoon, this problem disappeared on its own.
i5-12490F
Pylance can work independently.
The issue occurs when the Python extension is enabled alone—I've turned off all other extensions and kept only this one, and the problem still appears. This has been confirmed through thorough troubleshooting.
The Python environment output channel was crazily outputting [], and compared to today's normal situation,the Python output is just as I replied above.
You can ask AlexSSCoelho whether the issue has also been resolved in this VS Code update or not.
Activity
eleanorjboyd commentedon Mar 18, 2026
Hi! This appears to be empty— do you have specific data on the high CPU load to report?
AlexSSCoelho commentedon Mar 18, 2026
SaduluSama commentedon Mar 25, 2026
I'm experiencing this issue as well. Upon launching the editor, everything runs normally as long as I don't open any Python files. However, the moment I open one and the editor starts loading plugin services, my CPU usage spikes to near 100%.
The Python Language Server plugin works for a brief moment (about a minute), but then it gets interfered with by this specific plugin and stops functioning. This results in persistent high background CPU usage. I've tried different versions of the plugin, but the issue persists, so it doesn't seem to be version-specific. I suspect it might be caused by a recent VS Code update breaking compatibility.
After multiple attempts of closing and reopening the editor, it suddenly worked normally once, but closing and reopening it again reverted it back to the high CPU usage state. During this state, rendering becomes laggy. While syntax highlighting still works, features like comment hints, code completion (IntelliSense), go-to-definition, and code suggestions all fail. There is also about a one-second delay when pressing Enter.
After troubleshooting, I've ruled out conflicts with other extensions; this is definitely caused by the plugin itself.
SaduluSama commentedon Mar 25, 2026
Eleanor Boyd (@eleanorjboyd)
Alright, after I sent my previous reply and reopened it, it started working again:
Python output logs:
eleanorjboyd commentedon Mar 25, 2026
Hi AlexSSCoelho and @xihusuli,
Thank you for reporting this issue. To help us investigate the high CPU usage, we need some additional information:
[need] CPU Profile: as It's critical for identifying which code paths are consuming CPU.
[optional] Output Logs: Please provide the contents of:
[optional] Test without Pylance: Does the high CPU issue occur if you disable the Pylance extension? This would help us determine if the issue is in Python, Python Environments, or Pylance.
[optional] Extension list: Please share your installed extensions (
code --list-extensions).@xihusuli — I noticed your logs show a working session (Pylance starting successfully). Could you capture the logs during the high CPU/non-responsive state?
Thank you!
SaduluSama commentedon Mar 26, 2026
Eleanor Boyd (@eleanorjboyd)
There is good news—that it might be an issue with VS Code itself; after a small VS Code update yesterday afternoon, this problem disappeared on its own.
i5-12490F
Pylance can work independently.
The issue occurs when the Python extension is enabled alone—I've turned off all other extensions and kept only this one, and the problem still appears. This has been confirmed through thorough troubleshooting.
The Python environment output channel was crazily outputting [], and compared to today's normal situation,the Python output is just as I replied above.
You can ask AlexSSCoelho whether the issue has also been resolved in this VS Code update or not.
eleanorjboyd commentedon Apr 1, 2026
closing as this seems resolved- thanks!