libpurple Memory Cleanup
Nick Hebner
hebnern at gmail.com
Sun Mar 15 16:51:01 EDT 2009
libpurple does not clean up various memory allocations that it makes before
shutting down. While these do not affect memory usage during runtime, they
should still be cleaned up when we are done with them.
The attached patch cleans up most of the leaks that I could find in
libpurple and libjabber. libaim does not appear to leak any memory. I have
not checked out the other prpls as I am not using them, but I suspect that
some of them will need similar treatment.
I am still getting ~300 leaked blocks after my program closes, but the 10 or
so that I have investigated seem to originate from glib.
Thanks,
Nick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pidgin.im/pipermail/devel/attachments/20090315/3a76cb39/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: purple_leaks.patch
Type: application/octet-stream
Size: 27175 bytes
Desc: not available
URL: <http://pidgin.im/pipermail/devel/attachments/20090315/3a76cb39/attachment-0002.obj>
More information about the Devel
mailing list