After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 569696 - Memory leak in message-list
Memory leak in message-list
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.24.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[cleanup]
Depends on:
Blocks:
 
 
Reported: 2009-01-29 16:17 UTC by Srinivasa Ragavan
Modified: 2009-05-04 04:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24

Attachments
Patch for message-list (6.90 KB, patch)
2009-01-29 16:18 UTC, Srinivasa Ragavan 		committed Details | Review

Description Srinivasa Ragavan 2009-01-29 16:17:16 UTC 
Patch explains it all. Its not exactly a leak, but a built-up over a period of time. I have been using this patch for a month now. But I think it changes assumptions, so it must be reviewed for trunk.
Comment 1 Srinivasa Ragavan 2009-01-29 16:18:01 UTC 
Created attachment 127470 [details] [review]
Patch for message-list

I clear the internal gnode on regen. Its just that.
Comment 2 Milan Crha 2009-01-29 18:26:15 UTC 
If it works... :) it would take some time of testing to be more sure. If valgrind doesn't claim anything within, say half an hour, of usage, then why not, put it in, I would say.
Comment 3 Srinivasa Ragavan 2009-02-02 16:38:10 UTC 
mcrha, I had used totalview to figure this memory build up and its been fine. But I wanted some eye-balls on the code to be sure.
Comment 4 Srinivasa Ragavan 2009-02-25 07:57:03 UTC 
for 2.28.x
Comment 5 André Klapper 2009-05-03 19:29:52 UTC 
Evo has branched, can this get in now?
Comment 6 Srinivasa Ragavan 2009-05-04 03:30:42 UTC 
Should get in now.