Do you have a large history-limit and tmux has been running for a long time?
glibc can be a bit buggy about returning memory or address space to the OS, probably this is an example. You could try playing with the environment variables in mallopt(3), but I have never seen any evidence they do anything. Or modify tmux to call malloc_trim(0) (grid_destroy is a good place) or call it from gdb. On Tue, Nov 14, 2017 at 09:19:31PM +0100, Marcel Partap wrote: > Hi, > ok this is probably caused by my abusive "1" update-status-interval and the > scripts generating it.. but how can I track this down? It doesn't look sane > ???? > > > ------memory-usage----- --most-expensive- --out-of-memory--- ---procs--- > > ---system-- most-waiting-for --filesystem- -net/total- ----system---- > > [39362/39362] > > used free buff cach| memory process | kill score |run blk new| > > int csw | child process |files inodes| recv send| time > > 1848M 20.3G 99.7M 1322M|tmux 111G|chromium 305 | 27 3.0 > > 36|7936 5503 |systemd 1| 8640 53935 | 0 0 |30-10 20:57:47 > > 2199M 19.3G 115M 1977M|tmux 111G|chromium 304 | 20 1.0 85| > > 16k 6930 |nmon 0| 9056 56114 |2487B 218B|30-10 20:58:17 > > 2917M 17.6G 128M 3028M|tmux 111G|chromium 306 | 21 1.0 79| > > 18k 11k|chromium 2|10080 60053 | 92k 10k|30-10 20:58:47 > > 3855M 15.7G 130M 3971M|tmux 111G|chromium 307 | 16 1.0 75| > > 16k 7494 |tmux 0|10496 60436 | 52k 1718B|30-10 20:59:17 > > ... > > 15.2G 224M 148M 9546M|tmux 4019G|chromium 313 | 20 1.0 108| > > 18k 11k|tmux 2|22496 61855 |1310B 2988B|13-11 13:17:17 > > 15.3G 187M 147M 9555M|tmux 4019G|chromium 313 | 19 1.0 107| > > 18k 11k|tmux 2|22560 61900 | 109k 4736B|13-11 13:17:47 > > 15.3G 211M 153M 9465M|tmux 4019G|chromium 313 | 22 1.0 108| > > 19k 12k|tmux 2|22528 62312 | 282k 7359B|13-11 13:18:17 > > 15.4G 216M 154M 9423M|tmux 4019G|chromium 313 | 20 1.0 109| > > 18k 12k|tmux 2|22624 62429 | 26k 6112B|13-11 13:18:47 > > ... > > 11.8G 280M 10.7G 1940M|tmux 5169G|chromium 309 | 21 1.0 107| > > 20k 13k|tmux 2|17152 51211 |2141B 2896B|14-11 21:15:17 > > 11.8G 238M 10.7G 1992M|tmux 5169G|chromium 309 | 16 1.0 94| > > 20k 13k|boinc 1|17120 51158 |1814B 2833B|14-11 21:15:47 > > 11.8G 289M 10.7G 1938M|tmux 5169G|chromium 309 | 16 1.0 91| > > 20k 13k|tmux 2|17152 50608 |1971B 2812B|14-11 21:16:17 > > 11.8G 259M 10.6G 2051M|tmux 5169G|chromium 309 | 16 1.0 91| > > 20k 13k|tmux 2|17216 50603 | 14k 3013B|14-11 21:16:47 > > > > > Mem[||||||||||||||||||||||||||||||||||||||||||||||||||||||||||11.8G/23.5G] > > Tasks: 341; 12 running > > Swp[ > > 0K/0K] Load average: 17.37 18.56 18.94 > > > > Uptime: 15 days, 00:20:53 > > > PID User Command Swap USS PSS > > RSS > > 2466 root tmux -2 attach-session 0 208.0K 382.0K > > 2.6M > > 2792 empee584 tmux -2 attach-session 0 208.0K 385.0K > > 2.6M > > 15521 root tmux -L foo 0 224.0K 425.0K > > 1020.0K > > 15526 root tmux -L foo 0 143.7M 144.0M > > 144.7M > > 2794 empee584 tmux -2 attach-session 0 1014.1M 1014.4M > > 1016.6M > > 2468 root tmux -2 attach-session 0 1.2G 1.2G > > 1.2G > > ------------------------------------------------------------------------------- > > 6 2 0 2.4G 2.4G > > 2.4G > This with debian's tmux-2.6-1 .. > > #Regards/Marcel Partap > > -- > You received this message because you are subscribed to the Google Groups > "tmux-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send an email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "tmux-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
