Swap exhaustion

[Doug Hardie]

> On 27 May 2015, at 22:25, Michael Schuster <michaelsprivate at gmail.com> wrote:
> 
> Hi,
> 
> On Thu, May 28, 2015 at 7:09 AM, Doug Hardie <bc979 at 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).


The developer says that valgrind has been run on it extensively and no leaks have been found.  I suspect this is a “feature” that is being used in a way that was not expected and is using way more memory than one would expect.