On 15/04/14 08:14, Balazs Kezes wrote: > On 2014-04-14 11:57 +1200, Jan Larres wrote: >> I usually hit the problem when my machine becomes unresponsive for a >> while due to heavy swapping when starting a memory-heavy process. I'm >> not sure if that could cause fork() to fail, but it sounds like a >> possibility. > > Yeah. If you have large amounts of windows/panes all with large > scrollbacks then tmux can easily eat hundreds of MBs of memory. > Depending on your kernel's memory accounting settings (like the > overcommit setting) the kernel can decide that it will not allow the > fork to succeed but I don't know the details. Do you remember how big > was your tmux server and how much free RAM did you have when you seen > the problems?
I don't remember the exact numbers, but I do remember that often (or maybe even always, not sure) when this happened and I tried to open a new window it would fail with the message "failed to allocate memory" until I closed a few other windows, which sounds like your guess would be correct. -Jan ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
