On 2-Dec-07, at 12:03 PM, Christian Biere wrote: > Isn't there a counter which shows how often this leak occurs? If > there's only > one, there's probably some initialization the first time one of > these functions > is called and it's not really a leak. If this happens for each > handshake, that > would be something to look at.
It happens more than once, yeah. I think there were 20+ instances that accumulated over an hour or so. It's visible in the screenshots I sent you directly, to the left of the . So far, though, I don't have any easy way to export this information as text. Apple's command- line 'leak' tool might be an option, I'm not sure yet. so far I haven't gotten it to cough up a stack trace, which it's supposed to do. I'm not entirely sure the leak tracing relies on Dtrace, after all; it may just be the object history aspect of the 'Instrument' run tracing thing. > These two are not really memory leaks. They are not accumulating. It's > some memory allocated at startup used for the whole run time. It's > only > a "leak" in so far that the memory isn't released on exit. If I understand correctly, the leak reporting relies on whether or not there's a pointer to the memory block, or some such thing. It also relies on the use (ultimately) of the system's standard malloc, I think. The documentation is a bit above my comprehension level for regular casual reading, which is all I've done so far. I accept your assertion, but can't disambiguate. I'll ignore them in the future. ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ gtk-gnutella-devel mailing list gtk-gnutella-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
