https://clojure-lsp.io/troubleshooting/ has some tips

the logs contain some data about processing times which may indicate what's eating your cpu

Also, clojure-lsp needs more resources the first time it's scanning the deps of your project

Thank you, will explore those! And not, it was not the first time.

it's not the first time only, it can happen if your project.clj/deps.edn/etc was changed, so clojure-lsp needs to re-analyze the classpath

You caon confirm checking server log

might not be related, but I'm still having issues with completions (or something related to them) eating up my cpu(s). I'm still trying to create a public project which exhibits this problem, but real life gets in the way and I have very little time to work on it 😞

@U0178V2SLAY probably not related with completion, but didChange locking other features (like completion)

unfortunately I think only a repro would help to investigate that

yeah, I understand completely