This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-09-18
Channels
- # announcements (1)
- # babashka (15)
- # beginners (152)
- # calva (28)
- # circleci (1)
- # clj-kondo (24)
- # cljsrn (8)
- # clojure (137)
- # clojure-berlin (3)
- # clojure-czech (2)
- # clojure-dev (20)
- # clojure-europe (69)
- # clojure-finland (5)
- # clojure-france (3)
- # clojure-italy (11)
- # clojure-my (1)
- # clojure-nl (4)
- # clojure-uk (15)
- # clojuredesign-podcast (1)
- # clojurescript (13)
- # conjure (15)
- # cursive (13)
- # datomic (41)
- # deps-new (50)
- # events (1)
- # fulcro (9)
- # graalvm (27)
- # joker (2)
- # kaocha (11)
- # off-topic (22)
- # pathom (48)
- # rdf (6)
- # reagent (25)
- # reitit (47)
- # reveal (10)
- # ring-swagger (1)
- # rum (4)
- # sci (27)
- # shadow-cljs (73)
- # tools-deps (49)
- # vrac (2)
- # xtdb (4)
The floating window yet again froze my vim, and I managed to hit ctrl-c to interrupt it. After this, evaluations show this error
That's not good, I'm really sorry you've had to deal with that! I've never seen this before, not sure what the ml_get
part is :thinking_face:
Not sure how I'll reproduce this really, I don't know if anyone else has ever seen this?
It’s probably in a bad state right now. The interesting error might have been the one where I interrupted a stuck neovim (waiting for the floating window to appear, as mentioned before).
But, it turns out that there might be some leak of sorts somehow that grows with usage. A fresh instance of neovim starts off snappy, and then slowly all interactions are getting kind-of slower.
:thinking_face: I haven't seen it slow down overtime even working in my shared team pairing host (an AWS instance across the Atlantic for me with limited single core performance). I am fairly confident there's some mixture of plugins that's not working well together, but I'm not ruling out my code entirely of course. There definitely could be something wrong.
Knowing that it's a GUI frontend may come in handy since I've never tested Conjure in that sort of environment before. I can't imagine it'd make a difference, but maybe!
I'd love to have some input from other people that have experienced slow downs over time and weird errors from the log at any point. If there's a lurking performance bug I would love to squish it ASAP. I don't hit these issues on relatively limited machines, so it's surprising / confusing to me right now. Conjure really isn't doing much.
I do wonder if you can reproduce it without the GUI, might be interesting to see if that remains snappy in a terminal throughout the day?
I can see issues like "Frequent crashes when quitting VimR with 30+ buffers opened" on the repo which leans my concern towards VimR a little bit, but not entirely.
https://github.com/qvacua/vimr/issues/782 could also be related since conjure ends up creating a large buffer that is trimmed over time, vimr may be leaking memory in buffers that change a lot (like the conjure log)
Thanks for looking into this. The last issue does seem relevant, yes. Next week I’ll try a terminal session.
Not sure how I'll reproduce this really, I don't know if anyone else has ever seen this?
I'd love to have some input from other people that have experienced slow downs over time and weird errors from the log at any point. If there's a lurking performance bug I would love to squish it ASAP. I don't hit these issues on relatively limited machines, so it's surprising / confusing to me right now. Conjure really isn't doing much.