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

I tried to reproduce this by connecting to a server through Mosh,
running `while true; do man man | cat; done`, and watching the
mosh-client rss. Just for good measure, I resized the window a whole
bunch to trigger a flood of SIGWINCHes. mosh-client’s rss stayed
constant at around 8 MiB, so I think this has been fixed.

If you’re still having this issue, please reopen, and I’ll have another
look.