[Gllug] Troubleshooting Memory Leak

John Hearns hearnsj at googlemail.com
Wed Mar 25 11:19:51 UTC 2009


2009/3/24 James Laver <james.laver at gmail.com>:
>> Either way you'd be looking at a kernel bug. The kernel is supposed to
> protect you from sloppy code by cleaning up after processes that
> forget to deallocate memory, when the process terminates.

It may not be an application level problem.
I have seen network drivers causing memory problems - allocating large
amounts of slab memory.
This was admittedly some specialised low-latency drivers, but was a
kernel/driver issue nonetheless.
Diagnose using slabtop.
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug




More information about the GLLUG mailing list