Date: Mon, 16 Mar 2015 19:52:10 -0400 From: J David <j.david.lists@gmail.com> To: Konstantin Belousov <kostikbel@gmail.com> Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: Significant memory leak in 9.3p10? Message-ID: <CABXB=RSt0MgEyoJs4o5utTg7oSu0RZ%2B-czeY0k-Ro%2BfRubK3kQ@mail.gmail.com> In-Reply-To: <20150316232404.GM2379@kib.kiev.ua> References: <CABXB=RRhynY5FWvw3tHrLFRyitTemavXYLBpev5Mjs_kPqimXA@mail.gmail.com> <20150316232404.GM2379@kib.kiev.ua>
index | next in thread | previous in thread | raw e-mail
On Mon, Mar 16, 2015 at 7:24 PM, Konstantin Belousov <kostikbel@gmail.com> wrote: > There are a lot of possibilities to create persistent anonymous shared > memory objects. Not complete list is tmpfs mounts, swap-backed md disks, > sysv shared memory, possibly posix shared memory (I do not remember which > implementation is used in stable/9). If that's the explanation, how could it be detected/measured/investigated/resolved/prevented? Under ordinary circumstances, machines will go run like this for days/weeks: Mem: 549M Active, 3623M Inact, 567M Wired, 3484K Cache, 827M Buf, 3156M Free Swap: 1024M Total, 1024M Free Then, when this happens, it rapidly degrades from that to so bad that processes start getting killed for being out of swap space. Thanks!home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABXB=RSt0MgEyoJs4o5utTg7oSu0RZ%2B-czeY0k-Ro%2BfRubK3kQ>