Skip to content

Heavy CPU usage #2149 still an issue, prematurely closed #5124

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.

Sign up for GitHub

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

Jump to bottom
Closed
ctivanovich opened this issue Apr 5, 2019 · 2 comments
Closed

Heavy CPU usage #2149 still an issue, prematurely closed #5124

ctivanovich opened this issue Apr 5, 2019 · 2 comments

Comments

@ctivanovich
Copy link

Following the advice from this thread which was closed prematurely #2149, I switched to the Microsoft Python language server, but the same explosion in CPU/memory use I noted before disabling both Jedi and Pylint continued unabated using this server. My .py file is about 1200 lines of code, but it's the only one open and being linted/checked. This doesn't even consider what affect attempting to tab-complete or inspect a module might have.
Screenshot (32).
@ghost ghost added the triage-needed Needs assignment to the proper sub-team label Apr 5, 2019
@DonJayamanne DonJayamanne mentioned this issue Apr 5, 2019
Closed
@DonJayamanne
Copy link

Issue moved to Microsoft/python-language-server #891 via ZenHub

@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Apr 5, 2019
@DonJayamanne
Copy link

Moving to the upstream repo as thats where we're tracking issues related to the language server.

@lock lock bot locked as resolved and limited conversation to collaborators May 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DonJayamanne @ctivanovich