Is this happening in a bare emacs (with no additional packages loaded) as well? I'd try to isolate the package causing the problem by removing them one by one (or binary search).

Haven’t tried on a bare emacs, but debuging like that sounds kind of painful. Is there any way to log what’s going on?

Do you use clojure-lsp?

yes

Are you able to look at the processes? Also, please check lsp backend version.

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

It was my case.

hmm, yeah that might be the problem. I’ll try without that package and see if it gets fixed.

My case is fixed so it's important to have the latest version of the backend.

I see. Do you know if I update the clojure-lsp package does it update the lsp backend as well?

No, it should be done separately.

A trick that might or might not help you, if send emacs a SIGUSR2 signal it will interrupt whatever it's doing and enter the debugger. I've used this countless times to unjam an Emacs that's spinning at 100%, and the stacktrace can give you a hint of where the problem lies.

http://mbork.pl/2016-05-15_debug-on-whatever

e.g. killall -USR2 emacs on linux

sometimes it's so stuck that even this doesn't help, but it's worth trying

this will also turn on debut-on-quit, so it will enter the debugger every time you press C-g afterwards. You can turn that back off with M-x toggle-debug-on-quit

thanks plexus will try that