You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that opening a (very) large project in emacs sometimes causes clojure-lsp to throw an exception after a while.
The exception does not seem to break clojure-lsp, at least not in an obvious way. I can still invoke clojure-lsp functions from emacs and everything seems to work ok.
To Reproduce
Steps to reproduce the behavior:
Open a large project in emacs
Notice how clojure-lsp eats up all the cpu
Wait a few minutes
look at the clojure-lsp logs under /tmp and see an exception stack trace
Expected behavior
The exception should probably be handled within clojure-lsp.
Thanks for the report, It only affect linting the whole project after startup (which can be disabled with lint-project-files-after-startup?), it seems the channel clojure-lsp uses for diagnostics is reaching an overflow 🤔 I need to investigate the better way to fix it
@lassemaatta Fixed on master, would you mind try the fix before next release? you can clone clojure-lsp and run make to generate a clojure-lsp binary on the root. It'll not be compiled wtih GraalVM but it's enough to test if the issue was fixed
Describe the bug
I noticed that opening a (very) large project in emacs sometimes causes
clojure-lsp
to throw an exception after a while.The exception does not seem to break
clojure-lsp
, at least not in an obvious way. I can still invokeclojure-lsp
functions fromemacs
and everything seems to work ok.To Reproduce
Steps to reproduce the behavior:
clojure-lsp
eats up all the cpuclojure-lsp
logs under/tmp
and see an exception stack traceExpected behavior
The exception should probably be handled within
clojure-lsp
.Log output
User details (please complete the following information):
Linux archlinux 5.13.7-arch1-1
emacs
clojure-lsp 2021.08.03-13.33.03 | clj-kondo 2021.08.03
The text was updated successfully, but these errors were encountered: