[Pidgin] #3036: ICQ Memory Leak
Pidgin
trac at pidgin.im
Wed Sep 26 02:12:28 EDT 2007
#3036: ICQ Memory Leak
----------------------+-----------------------------------------------------
Reporter: Elendur | Owner: MarkDoliner
Type: defect | Status: new
Priority: minor | Milestone:
Component: ICQ | Version: 2.1.1
Resolution: | Keywords: memory leak icq
Pending: 1 |
----------------------+-----------------------------------------------------
Changes (by MarkDoliner):
* pending: 0 => 1
Comment:
Elendur: From the valgrind log it doesn't look like there was very much
that was actually LEAKING. So maybe memory is being allocated and there
are still references to it. When you were running Pidgin in Valgrind, how
did you stop it? By exiting Pidgin cleanly?
I can't reproduce this, so it's hard for me to debug it myself.
It might be beneficial to try using Valgrind's heap profiler, massif. You
can start it with something like "valgrind --tool=massif --format=html
pidgin" It'll create an HTML file and a .ps file in the current directory
that show where large chunks of memory were allocated. It sorts
allocations by space-time, so the results will be most useful if you can
make Pidgin allocate a lot of memory, and then sit there for a while not
doing anything. This obviously won't be possible if it just continues to
allocate memory until the end of time.
Also, a debug log from your AIM or ICQ session might be useful.
--
Ticket URL: <http://developer.pidgin.im/ticket/3036#comment:10>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list