Each clojure-lsp proccess represents a project, do you really have 6 projects opened?

even so, the first one is the one that is taking that much right?

yes, I really have 6 projects opened

and yes, only the first one, which is the clj-kondo one

Right, this should be no problem, since they consume less resource after started

does the clojure-lsp already started on the first one?

?

I mean, is it running or starting on the clj-kondo buffer (analyzing stuff etc)?

it starts happening while I've been working on it for a while

hum, so does starts correctly and after some time takes more cpu

yes

We could try something to check if it's the issue

add to .clj-kondo/config.edn

{:linters {:clojure-lsp/unused-public-var {:level :off}}} 

I already have :linters {:clj-kondo {:level :off}} in my config

hum, so it's probably not related with that linter

I have no idea, after startup things are really fast and consume few resources

I also can't really reproduce this, it just starts after a while, maybe after my laptop has been sleeping and then reopening

well I see 1 hour of that proccess running

so it could be something really hard to debug

meanwhile you can lsp-workspace-restart

will do

but sometimes I notice this only after a few hours, because I wear headphones

sounds odd indeed, some corner case where it may stuck in a loop or something

when you repro again, check https://clojure-lsp.io/troubleshooting/#server-log

Usually I open lots of projects(4-10) and some big ones on Nubank and never faced that before

maybe you will hit it when working on clj-kondo as well.

yes, maybe some corner case there

I will monitor the log file and then will come back to this when it happens again, thanks

So far no problems....

@U04V15CAJ, @ericdallo this often happens for me after merging, rebasing, or switching branches—something that changes a lot of files simultaneously. I think that’s why it often only happens many hours after opening a project.

It gets stuck in a loop re-analyzing a single file or a small set of files. The log fills up with lines that look like this:

2022-03-02T02:14:59.049Z  INFO [clojure-lsp.feature.file-management:?] - changes analyzed by clj-kondo took 0.06 secs

I enabled logging and will monitor - thanks

makes sense @U07M2C8TT, we do have a logic on didChangeWatchedFilles (that we should improve to consider branch changes)

@ericdallo ok, I'm in the loop state now

I could share my screen with you and we could try to diagnose

The log file keeps going with:

2022-03-04T14:01:58.171Z  INFO [clojure-lsp.feature.file-management:?] - changes analyzed by clj-kondo took 0.61 secs
2022-03-04T14:01:58.985Z  INFO [clojure-lsp.feature.file-management:?] - changes analyzed by clj-kondo took 0.81 secs
2022-03-04T14:01:59.555Z  INFO [clojure-lsp.feature.file-management:?] - changes analyzed by clj-kondo took 0.57 secs
2022-03-04T14:02:00.224Z  INFO [clojure-lsp.feature.file-management:?] - changes analyzed by clj-kondo took 0.67 secs
2022-03-04T14:02:00.931Z  INFO [clojure-lsp.feature.file-management:?] - changes analyzed by clj-kondo took 0.71 secs
2022-03-04T14:02:01.550Z  INFO [clojure-lsp.feature.file-management:?] - changes analyzed by clj-kondo took 0.62 secs
2022-03-04T14:02:02.361Z  INFO [clojure-lsp.feature.file-management:?] - changes analyzed by clj-kondo took 0.81 secs

I will end this soon as my laptop makes a lot of noise now

hmm, sorry, I'll abort it now... too stressful

this happened after git reset --hard

oh thanks

that helps a lot

so indeed it's related with watched file changes, I even think I know what could be

I'll investigate later today

thank you!

thank you too

I think we can do a repro creating 2 branches with a lot of changes one from the other

https://github.com/clojure-lsp/clojure-lsp/issues/796

My laptop doesn't have fans but I have also noticed than when switching branches etc lsp often “dies” as in it won't go to definitions or respond to commands. This is via calva, it gets stuck showing the progress bar which is normally not even noticeable.

I'm testing with Eric's new version (mentioned in that issue)

so far no problems