This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-09
Channels
- # adventofcode (187)
- # aws (1)
- # aws-lambda (1)
- # beginners (162)
- # boot (64)
- # cljs-dev (6)
- # cljsjs (2)
- # cljsrn (32)
- # clojure (357)
- # clojure-greece (1)
- # clojure-korea (4)
- # clojure-russia (63)
- # clojure-sanfrancisco (3)
- # clojure-spec (91)
- # clojure-uk (63)
- # clojurescript (74)
- # clojurex (10)
- # code-reviews (55)
- # core-async (4)
- # core-typed (1)
- # cursive (17)
- # datascript (36)
- # datomic (43)
- # devcards (4)
- # dirac (3)
- # emacs (59)
- # hoplon (286)
- # jobs-discuss (399)
- # luminus (4)
- # mount (9)
- # off-topic (30)
- # onyx (53)
- # protorepl (3)
- # re-frame (88)
- # reagent (4)
- # spacemacs (1)
- # specter (14)
- # untangled (1)
- # vim (42)
might be my imagination but repl memory leak seems worse in latest cursive. any thread dumps or whatever I can provide to help track down?
@bfabry I've noticed it too
I'm seeing this error repeatedly: Cannot init ReplState component state: encoded string too long: 73822 bytes
Does not seem to stop the REPL working but the error message is a bit annoying
Is there anything I can do to mitigate it ?
@val_waeselynck I’ve seen a few like that come through in the tracker. I’m not sure why this has suddenly started happening, it might have been an underlying IntelliJ change. If you delete <project>/.idea/replstate.xml
, you’ll lose your REPL history but it should fix the problem.
@bfabry @danielcompton: Sorry about that, I’m going to try to track that down today.
@cfleming thanks, tried that, no problem so far
@val_waeselynck Great, let me know if the problem comes back.
@bfabry and others, hopefully the memory issues are fixed in the latest EAP build, 1.4.2-eap1