[Bug 1766942] Re: tmux leaks memory in pane-border-status

2018-12-18 Thread Launchpad Bug Tracker
This bug was fixed in the package tmux - 2.6-3ubuntu0.1 --- tmux (2.6-3ubuntu0.1) bionic; urgency=medium * d/p/tmux-pane-border-status-leak.patch: Fixed memory leak in screen_redraw_make_pane_status (upstream fix). (LP: #1766942) -- Karl Stenerud Mon, 29 Oct 2018 19:33:11 +0

[Bug 1766942] Re: tmux leaks memory in pane-border-status

2018-12-18 Thread Brian Murray
I went ahead and tested this myself using the version of the package from bionic-proposed. root@tester:~# tmux -L none -f /dev/null new-session -s leaky-tmux-test 'tmux set-option -w -g pane-border-status top; tmux pipe-pane "cat>/tmp/leaky-tmux-test.log"; p=${TMUX#*,}; p=${p%,*}; s=0; j=0; echo

[Bug 1766942] Re: tmux leaks memory in pane-border-status

2018-12-17 Thread Łukasz Zemczak
Which package version has been used for verification? Please note that this information is required (as seen in #3 ). ** Changed in: tmux (Ubuntu Bionic) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1766942] Re: tmux leaks memory in pane-border-status

2018-12-14 Thread Karl Stenerud
** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766942 Title: tmux leaks memo

[Bug 1766942] Re: tmux leaks memory in pane-border-status

2018-12-13 Thread Karl Stenerud
Verified fix by running test case in https://code.launchpad.net/~kstenerud/ubuntu/+source/tmux/+git/tmux/+merge/357991 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766942 Title: tmux leaks memory

[Bug 1766942] Re: tmux leaks memory in pane-border-status

2018-11-05 Thread Brian Murray
Hello antgel, or anyone else affected, Accepted tmux into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tmux/2.6-3ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ub

[Bug 1766942] Re: tmux leaks memory in pane-border-status

2018-10-30 Thread  Christian Ehrhardt 
** Merge proposal linked: https://code.launchpad.net/~kstenerud/ubuntu/+source/tmux/+git/tmux/+merge/357991 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766942 Title: tmux leaks memory in pane

[Bug 1766942] Re: tmux leaks memory in pane-border-status

2018-10-30 Thread Karl Stenerud
** Changed in: tmux (Ubuntu Bionic) Status: Confirmed => In Progress ** Description changed: + [Impact] + + A memory leak in tmux causes it to eventually fail when run for long + periods of time. Since long term tmux sessions are common, this becomes + a real problem for sysadmins, etc. +

[Bug 1766942] Re: tmux leaks memory in pane-border-status

2018-10-29 Thread Karl Stenerud
** Changed in: tmux (Ubuntu Bionic) Assignee: (unassigned) => Karl Stenerud (kstenerud) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766942 Title: tmux leaks memory in pane-border-status To

[Bug 1766942] Re: tmux leaks memory in pane-border-status

2018-10-29 Thread Karl Stenerud
Confirmed the behavior with the following test from https://github.com/tmux/tmux/issues/1167#issuecomment-349040998 Run a simple/crude test in order to verify this finding: $ tmux -L none -f /dev/null new-session -s leaky-tmux-test 'tmux set-option -w -g pane-border-status top; tmux pipe-pane "c

[Bug 1766942] Re: tmux leaks memory in pane-border-status

2018-06-19 Thread  Christian Ehrhardt 
Hi antgel, I'm passing a few bugs with not enough attention atm. Your report is great - I put it in a queue to hopefully be picked up soon. Do you have a testcase other than waiting to see the issue? It is in screen_redraw_make_pane_status so maybe there is something that forces the redraw one co