[Evolution-hackers] Memory leak question in CamelImapCommand

2007-10-25 Thread Philip Van Hoof
Hi there, t almost sounds impossible but still, and that's why I ask. I noticed that the variable args in imap_command_strdup_vprintf is never freed. That would be a rather large memory leak (almost every IMAP command is created this way). So I'm a bit stunned that nobody else ever saw this one

Re: [Evolution-hackers] Memory leak question in CamelImapCommand

2007-10-25 Thread Matthew Barnes
On Thu, 2007-10-25 at 16:45 +0200, Philip Van Hoof wrote: Hi there, t almost sounds impossible but still, and that's why I ask. I noticed that the variable args in imap_command_strdup_vprintf is never freed. That would be a rather large memory leak (almost every IMAP command is created

Re: [Evolution-hackers] Memory leak question in CamelImapCommand

2007-10-25 Thread Philip Van Hoof
On Thu, 2007-10-25 at 11:02 -0400, Matthew Barnes wrote: On Thu, 2007-10-25 at 16:45 +0200, Philip Van Hoof wrote: The patch is of course a simple + g_ptr_array_free (args, TRUE); right before the return out;, right? ps. Adding Jeffrey in CC as I think he has a good idea how this