Date: Thu, 28 May 2015 07:25:47 +0200 From: Michael Schuster <michaelsprivate@gmail.com> To: Doug Hardie <bc979@lafn.org> Cc: kpneal@pobox.com, FreeBSD - <freebsd-questions@freebsd.org> Subject: Re: Swap exhaustion Message-ID: <CADqw_gLYnPnDFJjGvQfNRXBpKrVFKMnU%2BvKjcUQJYGU=19X14g@mail.gmail.com> In-Reply-To: <6F843A4D-8D2D-4DE2-B90E-A8033BEC1500@lafn.org> References: <1CD13C1C-5344-4909-A061-F25FBB86AFF9@lafn.org> <20150528000655.GA15385@neutralgood.org> <6F843A4D-8D2D-4DE2-B90E-A8033BEC1500@lafn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, 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. 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). regards Michael -- Michael Schuster http://recursiveramblings.wordpress.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADqw_gLYnPnDFJjGvQfNRXBpKrVFKMnU%2BvKjcUQJYGU=19X14g>