[kseistrup]

If you run e.g. btop or bpytop in a separate zellij tab, zellij will eventually gobble up all your memory and die.

In the beginning I wa very entusiastic and switched from tmux to zellij on remote machines, but as I usually have btop running in a tab it would die in a day or two, so now I'm back to using tmux on remote machines and reserve zellij for local (and make sure I don't run btop in a tab).

[kseistrup]

(Does HN have an indentation limit, I can't seem to reply to imsnif…)

I'm always running the latest zellij, but I'll start btop in a tab right away and see what happens.

I did mention it in https://github.com/zellij-org/zellij/issues/1625#issuecommen... and noticed the issue is still open, so I haven't tried btop in zellij since v0.36.0.

[imsnif]

Keeping track is hard sometimes, I saw it again in the issue as you mentioned. :)

[imsnif]

I'm like 90% sure this was fixed - if you'd be willing to try with a recent Zellij version, that would be great.

Otherwise, I'll try your reproduction myself and will fix if I can reproduce. Thanks.

[kseistrup]

I'm now running v0.37.2 on a remote machine with 3 tabs: a shell, syslog spooled by lnav, and btop. To me it looks like it grows by 2 kB RAM every minute. I am logging to a file with timestamps, and we will see the results tomorrow.

[kseistrup]

In the course of less than 12 hours zellij grew from 93 MB to 1227 MB in roughly 2 kB increments per minute. Closing the tab running btop will release the stolen memory.

I will append a comment to the Microsoft GitHub issue mentioned above a little later.

[imsnif]

Thanks! If you could also specify how you measured it and attach some debug logs (there are instructions in the issue template) that would be great. Because my instance has run overnight without issue and I'd love to be able to reproduce this.

[kseistrup]

I entered a comment ( https://github.com/zellij-org/zellij/issues/1625#issuecommen... ) before I read your comment here. Please let me know if that is sufficient.