| 2018-04-25 17:44:44 |
antgel |
bug |
|
|
added bug |
| 2018-06-19 12:47:07 |
Christian Ehrhardt |
tmux (Ubuntu): status |
New |
Fix Released |
|
| 2018-06-19 12:47:13 |
Christian Ehrhardt |
nominated for series |
|
Ubuntu Bionic |
|
| 2018-06-19 12:47:13 |
Christian Ehrhardt |
bug task added |
|
tmux (Ubuntu Bionic) |
|
| 2018-06-19 12:47:33 |
Christian Ehrhardt |
bug |
|
|
added subscriber Ubuntu Server |
| 2018-06-19 12:47:39 |
Christian Ehrhardt |
tags |
|
server-next |
|
| 2018-06-19 12:53:20 |
Christian Ehrhardt |
tmux (Ubuntu Bionic): status |
New |
Confirmed |
|
| 2018-10-29 13:13:46 |
Karl Stenerud |
bug watch added |
|
https://github.com/tmux/tmux/issues/1167 |
|
| 2018-10-29 14:56:27 |
Karl Stenerud |
tmux (Ubuntu Bionic): assignee |
|
Karl Stenerud (kstenerud) |
|
| 2018-10-30 07:30:41 |
Karl Stenerud |
tmux (Ubuntu Bionic): status |
Confirmed |
In Progress |
|
| 2018-10-30 07:30:58 |
Karl Stenerud |
description |
The upstream bug is reported and fixed at https://github.com/tmux/tmux/issues/1167.
Can we either patch the package (patch at https://github.com/tmux/tmux/commit/c363c236aaea5b7a879493d8f3c85bead546f063) or upgrade to 2.7 (I guess this is less likely to happen given the imminent release). |
[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.
[Test Case]
# apt update
# apt dist-upgrade -y
# apt install -y tmux
# 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 "ITER: RSZ"; while [ $j -lt 6000 ] ; do j=$((j+1)); n=$(ps hwo rsz $p); printf "\e]2;%d: %d\e\\\\\r%4d: %d" $j $n $j $n; [ $s -ne $n ] && { echo; s=$n; }; done'
[exited]
# cat /tmp/leaky-tmux-test.log ; echo
ITER: RSZ
1: 3712
1360: 3776
2725: 3904
4215: 4032
5743: 4160
6000: 4160 (example output)
RSZ will only change during the test if there's a memory leak. By comparison, we get correct behavior running without pane-border-status top:
$ tmux -L none -f /dev/null new-session -s leaky-tmux-test 'tmux pipe-pane "cat>/tmp/leaky-tmux-test.log"; p=${TMUX#*,}; p=${p%,*}; s=0; j=0; echo "ITER: RSZ"; while [ $j -lt 6000 ] ; do j=$((j+1)); n=$(ps hwo rsz $p); printf "\e]2;%d: %d\e\\\\\r%4d: %d" $j $n $j $n; [ $s -ne $n ] && { echo; s=$n; }; done'
[exited]
$ cat /tmp/leaky-tmux-test.log ; echo
ITER: RSZ
1: 3492
6000: 3492
[Regression Potential]
Since this is only plugging a memory leak, no other behavior should be affected.
[Original Description]
The upstream bug is reported and fixed at https://github.com/tmux/tmux/issues/1167.
Can we either patch the package (patch at https://github.com/tmux/tmux/commit/c363c236aaea5b7a879493d8f3c85bead546f063) or upgrade to 2.7 (I guess this is less likely to happen given the imminent release). |
|
| 2018-10-30 10:51:09 |
Christian Ehrhardt |
merge proposal linked |
|
https://code.launchpad.net/~kstenerud/ubuntu/+source/tmux/+git/tmux/+merge/357991 |
|
| 2018-11-05 23:00:31 |
Brian Murray |
tmux (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2018-11-05 23:00:32 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-11-05 23:00:34 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2018-11-05 23:00:39 |
Brian Murray |
tags |
server-next |
server-next verification-needed verification-needed-bionic |
|
| 2018-12-14 09:02:09 |
Karl Stenerud |
tags |
server-next verification-needed verification-needed-bionic |
server-next verification-done verification-done-bionic |
|
| 2018-12-17 10:00:37 |
Łukasz Zemczak |
tmux (Ubuntu Bionic): status |
Fix Committed |
Incomplete |
|
| 2018-12-18 21:36:18 |
Launchpad Janitor |
tmux (Ubuntu Bionic): status |
Incomplete |
Fix Released |
|
| 2018-12-18 21:36:22 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
