-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Analysis of peewee with the new LS never finishes #2682
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
Comments
Can you please verify, @ericsnowcurrently ? |
Thanks for letting us know about this problem, @albireox. I'm having trouble reproducing the behavior that you're reporting. Here's what I did:
When I did that, everything resolved almost immediately (with no high CPU/RAM usage). I could tell the language server was done processing because the Are there any other details that would help us sort this out? FYI, I am using Ubuntu linux. It's possible that the problem is Mac-specific. Is there any way you could try this out on linux to see if you get the same behavior? Either way, we'll work on trying it out on Mac. |
I tried this on Mac and found that the language server appears to be starting still. Hover tooltips all show |
Thanks for looking into this @ericsnowcurrently. Unfortunately I don't have a Linux box handy to test this. The steps you describe are what cause the problem for me. I jus tested it with the latest versions of vscode-insiders, vscode-python, and python-language-server and still get the large usage of resources. The RAM usage in particular never seems to stop growing. In my case the hover tooltips seem to work, I'm seeing the linter output, but nothing in the outline. |
I can confirm that PR201 from |
@MikhailArkhipov fyi |
Environment data
Actual behavior
I have a local checked out version of peewee. When the new LS tries to analyse the main file,
peewee.py
, it uses >100% of CPU and the RAM usage increases continuously (over 40GB at some point). This doesn't seem to complete, even after leaving it open and running for an hour. Things like theGo to symbol
list never get rendered.Expected behavior
Less use of resources.
Steps to reproduce:
The text was updated successfully, but these errors were encountered: