Skip to content
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

Nimsuggests spins with 100% CPU usage #111

Open
mratsim opened this issue Dec 9, 2019 · 6 comments
Open

Nimsuggests spins with 100% CPU usage #111

mratsim opened this issue Dec 9, 2019 · 6 comments

Comments

@mratsim
Copy link

mratsim commented Dec 9, 2019

Not sure what triggers it, but poor laptops:

DeepinScreenshot_select-area_20191208230303

@saem
Copy link

saem commented Dec 27, 2020

This isn't actionable, at best I'm guessing you're using it with weave, also since there are number of these processes, you're probably using the vscode extension. It'll trigger suggestion requests when you mouse over a new symbol to do a definition look up.

The project file should be part of the command line that htop output is showing so at least the startup parameters for the nimsuggest process can be isolated. If you're willing to run a dev version of the nim version of the vs code extension there is enough console.log statements that it shouldn't be too hard to isolate the call.

Otherwise, I'd suggest closing this issue for now.

@inv2004
Copy link

inv2004 commented Feb 7, 2021

I had the problem in project with a lot of macros, and I thought it was the reason,

but yesterday I found CPU eating on a simple project without templates at all.

Probably the most annoying issue about nimsuggest on laptops

@saem
Copy link

saem commented Feb 7, 2021

Is the project simple enough to shrink down and meaningless enough to post as an example?

@inv2004
Copy link

inv2004 commented Feb 7, 2021

@saem
Copy link

saem commented Feb 7, 2021

Simple one: https://github.com/inv2004/youtag

Which file was it? nimsuggest is started with a project file, so need to know that as well.

@inv2004
Copy link

inv2004 commented Feb 7, 2021

@saem
Just turned it on again and it looks ok. I suppose that the problem happens during some changes - I will ping you here as soon as it appears again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants