Date: Mon, 29 Dec 2008 11:13:53 +0100 From: =?ISO-8859-2?Q?Nikola_Kne=BEevi=E6?= <laladelausanne@gmail.com> To: freebsd-hackers@freebsd.org Subject: Re: debugging mbuf allocation/dealocation Message-ID: <DFC7E12E-3FE7-47F0-A7C7-6FBF042581D1@gmail.com> In-Reply-To: <alpine.BSF.1.10.0812271720510.47096@fledge.watson.org> References: <623D1024-5DA0-4252-8DA9-FA86E0407DA8@gmail.com> <alpine.BSF.1.10.0812271720510.47096@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > You can use the KTR(4) facility to trace memory allocations and > deallocations, logging them to memory, disk, etc. Unfortunately > interpreting the data can be fairly tricky, as network leaks tend to > happen over a long period of time, be stored in sockets, etc, but > it's definitely possible and has been done. :-) Processing the > results with a perl script goes a long way, as the allocated/freed > pointers are included, etc. Hi Robert, thanks for the pointers :) I discovered that root cause of the leakage - Click::Packet had a bad destructor, which wasn't free-ing mbufs all the time. Since there are some other forms of leaking in Click, I'll use KTR do discover them. Cheers, Nikola
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DFC7E12E-3FE7-47F0-A7C7-6FBF042581D1>