Bugzilla – Bug 30
process_Dreply leaks memory
Last modified: 2009-12-29 15:48:48 MST
You need to
before you can comment on or make changes to this bug.
Each call to process_Dreply leaks a few bytes of memory
revision 3126. Fixed in 2.3-fixes
looks like this fix was backed out because it can cause a double free.
Do you know where else it was free'd? what if instead of just freeing it you
also set the pointer to NULL. If we check for NULL before any attempt to free
this memory, then we should avoid a double free.
The original fix that was backed out set the pointer to NULL after the free but
it appears the memory is freed in other functions as well. We might want to
check all free operations and set pointers to NULL if appropriate.
This is a test to see if Bugzilla is now sending e-mail to torquedev.
This is another test.
adding torquedev to the CC list for the bug