Memory leaks in win pidgin 2.5.1?

[Daniel Atallah]

On Tue, Sep 9, 2008 at 3:28 AM, dave1g <dave1g at satx.rr.com> wrote:
>
> found this GPLed sf project  winleak - it was able to read pidgins symbols.
> http://sourceforge.net/projects/winleak/
>
> attached is the output of running pidgin for a few minutes...doing almost
> nothing so its a bit surprising it was limited to keeping track of 50
> stacks.  http://www.nabble.com/file/p19387252/MemoryHooksReport.txt
> MemoryHooksReport.txt

Most of these are probably not accurate (although this looks like it
might be a tool with potential).  In order to get more accurate
information, you'll need to set the G_DEBUG and G_SLICE environment
variables as mentioned on the "Running Glib Applications" page:
http://library.gnome.org/devel/glib/stable/glib-running.html

Specifically:

G_DEBUG=gc-friendly
and
G_SLICE=always-malloc

-D