This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-09-10
Channels
- # announcements (16)
- # aws (1)
- # babashka (2)
- # beginners (33)
- # biff (2)
- # clj-kondo (13)
- # cljs-dev (1)
- # cljsrn (3)
- # clojars (6)
- # clojure (198)
- # clojure-australia (3)
- # clojure-europe (41)
- # clojure-france (3)
- # clojure-nl (2)
- # clojure-spec (7)
- # clojure-uk (12)
- # clojurescript (57)
- # clojureverse-ops (1)
- # code-reviews (3)
- # community-development (2)
- # conjure (10)
- # data-science (1)
- # datomic (15)
- # depstar (2)
- # docker (2)
- # etaoin (1)
- # events (1)
- # exercism (5)
- # fulcro (23)
- # helix (23)
- # introduce-yourself (4)
- # jobs (6)
- # kaocha (1)
- # lsp (11)
- # meander (107)
- # off-topic (8)
- # pathom (3)
- # polylith (33)
- # re-frame (23)
- # reagent (7)
- # reitit (28)
- # remote-jobs (3)
- # sci (1)
- # shadow-cljs (2)
- # specter (5)
- # sql (38)
- # tools-deps (72)
- # web-security (9)
- # xtdb (32)
clojure-lsp (which I use via IntelliJ) easily consumes 100s of % of CPU on my new Mac. Is it common? Any tips how to troubleshoot and ameliorate?
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
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)
yeah, I understand completely