Date: Thu, 28 May 2015 01:06:23 -0700 From: Doug Hardie <bc979@lafn.org> To: Michael Schuster <michaelsprivate@gmail.com> Cc: kpneal@pobox.com, FreeBSD - <freebsd-questions@freebsd.org> Subject: Re: Swap exhaustion Message-ID: <CE83054D-DBE3-4176-8613-4D20E0C216FD@lafn.org> In-Reply-To: <CADqw_gLYnPnDFJjGvQfNRXBpKrVFKMnU%2BvKjcUQJYGU=19X14g@mail.gmail.com> References: <1CD13C1C-5344-4909-A061-F25FBB86AFF9@lafn.org> <20150528000655.GA15385@neutralgood.org> <6F843A4D-8D2D-4DE2-B90E-A8033BEC1500@lafn.org> <CADqw_gLYnPnDFJjGvQfNRXBpKrVFKMnU%2BvKjcUQJYGU=19X14g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 27 May 2015, at 22:25, Michael Schuster <michaelsprivate@gmail.com> = wrote: >=20 > Hi, >=20 > On Thu, May 28, 2015 at 7:09 AM, Doug Hardie <bc979@lafn.org> wrote: > If I am understanding correctly, then it appears that a process can = actually allocate enough memory to eat up the swap space. Then I need = to find out why that process is allocating so much memory. Thanks. >=20 > one scenario that comes to mind is memory leak - I'd guess at a code = path where a previously allocated chunk or memory isn't properly = free()d. I'd start debugging using the information in malloc(3). The developer says that valgrind has been run on it extensively and no = leaks have been found. I suspect this is a =E2=80=9Cfeature=E2=80=9D = that is being used in a way that was not expected and is using way more = memory than one would expect.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CE83054D-DBE3-4176-8613-4D20E0C216FD>