Fork me on GitHub
#conjure
<
2020-09-18
>
orestis14:09:51

The floating window yet again froze my vim, and I managed to hit ctrl-c to interrupt it. After this, evaluations show this error

👀 3
orestis14:09:51

And the floating window is now stuck 😂

Olical14:09:10

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:

Olical14:09:25

Not sure how I'll reproduce this really, I don't know if anyone else has ever seen this?

orestis14:09:36

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).

orestis14:09:22

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.

orestis14:09:34

I’m using VimR, not sure if it makes any difference or not.

Olical14:09:53

: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.

Olical14:09:09

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!

Olical14:09:23

It might not handle massive long buffers as well as the TUI versions?

Olical14:09:49

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.

Olical14:09:06

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?

Olical14:09:09

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.

Olical15:09:56

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)

orestis18:09:46

Thanks for looking into this. The last issue does seem relevant, yes. Next week I’ll try a terminal session.

Olical14:09:25

Not sure how I'll reproduce this really, I don't know if anyone else has ever seen this?

Olical14:09:49

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.