All I have is:

(clojure :variables
              clojure-backend 'cider
              clojure-enable-clj-refactor t
              clojure-enable-linters 'clj-kondo)

The official guide to the Clojure layer is at https://develop.spacemacs.org/layers/+lang/clojure/README.html#enabling-sayid-or-clj-refactor Yes, @didibus is correct that clj-refactor and other features are optional on the layer. Any http://www.spacemacs.org layer documentation is likely to be several years out of date, so the http://develop.spacemacs.org version should be used. develop branch has been the default branch for a long time now, and the defacto branch used for many years.

You could also refer to https://practical.li/spacemacs/ which uses the develop branch of Spacemacs

i'm going to see if re-naming it does anything, just bc i have no idea what better to do.

yes. re-naming it means it doesn't crash. I can reliable crash emacs just with that specific name.

hmmmm

maybe bc it starts with "comment"?

I wonder if its Emacs that is using the CPU or is Emacs blocked by a process it shelled out to that is using the CPU? e.g. clojure-lsp ? Perhaps look at the spawned processes as the mouse moves over that name https://practical.li/spacemacs/install-spacemacs/troubleshooting.html#issues-with-spawned-processes If Emacs lsp-ui has the docs mouse over docs enabled, you may have found a bug with lsp-ui or possibly clojure-lsp

I don't think it's LSP related but you never know 😂 I suspect it could be related to clojure-mode or something, I suggest you toggle-debug-on-quit and when everything freezes or cause the issue hit C-g to get a stack where emacs was

I’ve had freezes too, always when interacting with functions whose name starts with “comment”! For me, I don’t think it was on hover, though I can’t remember perfectly. I’d also be surprised if it’s clojure-lsp, since clojure-lsp operates primarily on tokens (i.e. the full function name), not parts of tokens. But you never know.

I've just sent the CPU to over 100% after typing in comment-selection which should have been a snippet that expanded, but it wasn't recognised as a snippet and now Emacs is keeping my laptop warm... TAB or j with the cursor over comment sends the Emacs process into a frenzy... C-g stops what ever process is using all the cpu...

Interesting. Logging the commands I get C-g pupo/close-window which seems to suggest that purpose-popwin is trying to do something. Could the auto-completion be using purpose-powin to draw the popups and somehow be getting stuck trying to do something?

never heard of that package/function 😂 which package calls it in the stack? lsp-mode/clojure-mode etc

There is a backtrace here https://gist.github.com/practicalli-john/278b8d8ec30deab3fb162405dd2c98ad

line 38 has an lsp process

still, it seems to come from clojure--looking-at-non-logical-sexp , clojure-mode

I can instantly fix the issue by running lsp-workspace-shutdown

but then I dont have LSP anymore and I am sad 😞

probably lsp is trying to do something that under the hood end up calling a clojure-mode function which causes that

seems like a case of clojure-mode conflicting with clojure-lsp in some strange way as it just doesnt happen with lsp disabled

so the fix would be on clojure-mode still

yeah, it's the lsp hover feature, which tries to color the token using the major mode, in this case clojure-mode, which seems that function has some performance regex issue

if you manage to repro calling that function manually, you could open a issue on clojure-mode

Is that the hover feature for docs, or for auto-complete (or are they the same thing)

docs

Ah yes, if I disable docs popup completely then I do not get the lockup with lsp running. Initially I had disabled the docs popup for the cursor but not for mouse, so a little strange ciojure-mode is causing a lockup. I will try and see if I can figure out something meaningful to report on clojure-mode Thank you.

yeah, probably the issue is that the hover docs show markdown clojure code, and to color that markdown we call the major mode which knows how to color it, in this case clojure-mode

Hmm, I has assumed there wouldnt be any docs for the piece of text by itself, i.e. comment-seperatoror (spelt incorrectly on purpose) yet lsp seems to be trying to font lock the markdown for it. Is this normal?

lsp--fontlock-with-mode("

\n\n----\n\n*[/home/..." lsp--render-markdown)
  lsp--render-string("

\n\n----\n\n*[/home/..." "markdown")
  lsp--render-element(#<hash-table equal 2/2 0x1591b67bd835>)
  #f(compiled-function (contents server-id) #<bytecode 0x7a9334e0f6d7b8a>)(#<hash-table equal 2/2 0x1591b67bd835> clojure-lsp)
  apply(#f(compiled-function (contents server-id) #<bytecode 0x7a9334e0f6d7b8a>) #<hash-table equal 2/2 0x1591b67bd835> clojure-lsp nil)
  lsp-clients-extract-signature-on-hover(#<hash-table equal 2/2 0x1591b67bd835> clojure-lsp)

Oh, it seems like lsp is rendering docs for text, although if I change the text and hover over with the mouse the doc is for the previous text.. very strange..

This is quite curious. Originally the text was comment-separatoror and then I change it to fish-and-chips and when I hover over with the mouse I get a doc with the previous text.

Sounds like outdated analysis from clojure-lsp, although not related to the performance issue

I think its because the backtrace has stopped everything in Emacs. I guess that is how it works, first time I've tried to use it in a while. I've had to reboot emacs.