Package: mosh
Version: 1.2.5-1
Severity: normal

There seems to be a memory leak in mosh-client; two of my processes (for 
different servers) already use 300 resp. 340 MB RAM (top output):

 5855 .  20  0  375540 339864  5600 S   0,0  3,0  11:30.68 mosh-client ...
 5859 .  20  0  327628 291856  5512 S   0,3  2,6  19:03.22 mosh-client ...

I'm using mosh to access internal server from my notebook.
That means that when I'm at home or in the train, the connection is broken 
for some time.

I guess that's one of the factors at play here; another server that I can 
reach more or less continuously uses far less memory, although it's the 
same age:

 30307.  20  0   50496  14408  5220 S   0,0  0,1  21:24.55 mosh-client ...


Thanks for listening.


(Please note that I can't install +b2 from unstable because of the gcc-5 
transition, so in case that would've fixed it, please accept my apologies.)


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mosh depends on:
ii  dpkg            1.18.3
ii  libc6           2.19-22
ii  libgcc1         1:5.1.1-14
ii  libprotobuf9    2.6.1-1
ii  libssl1.0.0     1.0.2d-1
ii  libstdc++6      5.1.1-14
ii  libtinfo5       6.0+20151024-2
ii  libutempter0    1.1.6-1
ii  openssh-client  1:6.9p1-2+b1
ii  zlib1g          1:1.2.8.dfsg-2+b1

Versions of packages mosh recommends:
ii  libio-socket-ip-perl              0.37-1
ii  perl-base [libio-socket-ip-perl]  5.20.2-6

mosh suggests no packages.

-- no debconf information

Reply via email to