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

100% CPU utilization #190

Open
jagjordi opened this issue May 21, 2024 · 2 comments
Open

100% CPU utilization #190

jagjordi opened this issue May 21, 2024 · 2 comments

Comments

@jagjordi
Copy link
Contributor

I am getting 100% CPU utilization whenever I open a SV file
image
I am using NeoVim and LSP config to enable Veridian.
In the LSP logs I don't see anything abnormal:

[ERROR][2024-05-21 15:46:33] .../vim/lsp/rpc.lua:734	"rpc"	"/sbin/veridian"	"stderr"	"INFO [veridian] starting veridian...\nINFO [veridian::server] found config: veridian.yml\nINFO [veridian::server] reading config file\nINFO [veridian::server] enabled linting with slang\nINFO [veridian::server] enabled linting with verilator\nINFO [veridian::server] enabled formatting with verible-verilog-format\n"

Can you give some pointers to trace down this issue?

@jagjordi
Copy link
Contributor Author

It turned out I had a DesignWare directory in my path and I guess the parser got overloaded trying to parse all the modules. I moved it somewhere else and it works now. Maybe a nice addition would be to have a exclude pattern or a similar type of mechanism

@vivekmalneedi
Copy link
Owner

That's funny, the server design there is not great and it tries to start a thread to run the parser for every file it can find. It should be using a threadpool or just be hooked into the existing async runtime.
An exclude option is a good idea. Though I guess another workaround would be to turn off auto_search_workdir.

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

2 participants