-
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
Microsoft.Python.LanguageServer infinite cycle (analysis) and high resource usage #5005
Comments
I'm glad to see someone already raised this issue. This exact same problem started happening to me fairly recently. My development environment:
Memory usage sometimes goes over 16GB on my machine with 32GB RAM! |
Looks like the same issue upstream as microsoft/python-language-server#832 |
i am going through with same issue |
We are working on reducing the memory overhead of analysis, and should have some improvements within a few days. In the meanwhile if this is impacting your productivity you can set jediEnabled to true in the Python extension settings to use jedi for analysis. |
Closing in favor of microsoft/python-language-server#832 |
Environment data
Expected behaviour
Can
Analyzing in background, xxxx items left...
in a reasonable amount of time using a reasonable amount of resources.Actual behaviour
Continousuly
Analyzing in background, xxxx items left...
using several gigabytes of RAM and large amounts of CPU.I believe it is related to any of the issues microsoft/python-language-server#546 was supposed to solve.
Steps to reproduce:
virtualenv
andpip install dash_html_components
import dash_html_components as html
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
; turn on source maps to make any tracebacks be useful by runningEnable source map support for extension debugging
)(As far as I can tell, this information will not be helpful)
The text was updated successfully, but these errors were encountered: