Veridian always pegs 2 cores, even when no changes have happened

vivekmalneedi / veridian

A SystemVerilog Language Server

MIT License

134 stars 15 forks source link

Veridian always pegs 2 cores, even when no changes have happened #177

Closed nuudlman closed 1 year ago

nuudlman commented 1 year ago

Just having a vscode workspace that has (system)verilog in it is enough to start veridian, even if no (system)verilog file is open or has changed: Screenshot_20230703_150846 Screenshot_20230703_151111

nuudlman commented 1 year ago

Looks like this is a issue with the BlueSpec Verilog extension and not Veridian, so I will go ahead and close this