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 626180 - CamelFolder leakage ?
CamelFolder leakage ?
Status: RESOLVED NOTABUG
Product: evolution
Classification: Applications
Component: Mailer
2.32.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks: 627707
 
 
Reported: 2010-08-06 10:12 UTC by Michael Meeks
Modified: 2013-03-20 08:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
debugging patch (1.68 KB, patch)
2010-08-06 10:13 UTC, Michael Meeks
none Details | Review

Description Michael Meeks 2010-08-06 10:12:55 UTC
Worried about bug#622366 and the runaway leakage, I knocked up this quick patch to track CamelFolders [ nice that it's now a GObject I guess ].

Having started Evo, and prodded about at a few folders, I exited.

Imagine my surprise ;-) to discover see that every folder I had visited was still live in memory: is that deliberate ? Do we intent to keep CamelFolders around indefinitely ? [ do we reduce their resource usage somehow if they are not visible so it doesn't matter ? ]

24 objects leaked
        0x80a1cf8       CamelMboxFolder 155     'Templates'     'Templates'
        0xa76ba08       CamelMboxFolder 3       'demo'  'Mail/demo'
        0x80a19b8       CamelMboxFolder 6       'Inbox' 'Inbox'
        0x8abf558       CamelMboxFolder 4       'framework'     'Mail/1OpenOffice/oolists/framework'
        0x86f7ae8       CamelVTrashFolder       4       'Junk'  '.#evolution/Junk'
        0x80a1c28       CamelMboxFolder 5       'Sent'  'Sent'
        0x86f7918       CamelVTrashFolder       1       'Junk'  '.#evolution/Junk'
        0x87cce20       CamelIMAPXFolder        5       'INBOX' 'INBOX'
        0x8acd6b8       CamelVTrashFolder       3       'Trash' '.#evolution/Trash'
        0xa76b938       CamelMboxFolder 3       'a11y'  'Mail/a11y'
        0x8acd318       CamelVTrashFolder       3       'Junk'  '.#evolution/Junk'
        0x87ccef8       CamelIMAPXFolder        9       'INBOX' 'INBOX'
        0x8abf488       CamelMboxFolder 4       'opensuse-noise'        'Inbox/opensuse-noise'
        0x87ad818       CamelIMAPXFolder        4       'Cabinet'       'Cabinet'
        0x80a1b58       CamelMboxFolder 5       'Outbox'        'Outbox'
        0xa76b868       CamelMboxFolder 3       '1freedesktop'  'Mail/1freedesktop'
        0x8add2a0       CamelVeeFolder  2       'Unmatched'     'UNMATCHED'
        0x87ad8f0       CamelIMAPXFolder        4       'Checklist'     'Checklist'
        0x8abf6f8       CamelMboxFolder 3       'Mail'  'Mail'
        0x86f7a00       CamelVTrashFolder       3       'Trash' '.#evolution/Trash'
        0x86f7830       CamelVTrashFolder       1       'Trash' '.#evolution/Trash'
        0xa76bad8       CamelMboxFolder 3       'gnome-announce'        'Mail/gnome-announce'
        0x80a1a88       CamelMboxFolder 5       'Drafts'        'Drafts'
        0x8abf628       CamelMboxFolder 4       'gnumeric'      'Mail/archive/gnumeric'

HTH.
Comment 1 Michael Meeks 2010-08-06 10:13:34 UTC
Created attachment 167243 [details] [review]
debugging patch
Comment 2 Matthew Barnes 2010-08-06 12:18:31 UTC
I know we cache CamelFolderInfos in such places as mail/em-folder-tree.c and mail/mail-folder-cache.c, so I doubt the CamelFolders themselves are meant to be kept around indefinitely.  The aforementioned source files is where I would begin hunting.

See also my comments in bug #622366.
Comment 3 Milan Crha 2013-03-20 08:07:14 UTC
The Trash and Junk folders keep track of opened folders in respective stores, unless a real Trash/Junk folders are selected (on IMAP side currently). Thus this is not a bug. The 155 ref-count on Templates is suspicious, but I've a feeling it was addressed during the last 2 years. In any case, you've opened bug #627257 for the Templates, thus let's investigate there.