GNOME Bugzilla – Bug 332931
double free or corruption when editing values
Last modified: 2007-08-27 13:10:09 UTC
Everytime when editing a value in reciently built gconf. *** glibc detected *** double free or corruption (out): 0x082929d0 *** Backtrace:
+ Trace 66592
Me too. (jhbuild HEAD compiled on Ubuntu 5.10) (gdb) run Starting program: /opt/gnome2/bin/gconf-editor [Thread debugging using libthread_db enabled] [New Thread -1226869056 (LWP 7449)] GTK Accessibility Module initialized Bonobo accessibility support initialized *** glibc detected *** double free or corruption (out): 0x08289830 *** Program received signal SIGABRT, Aborted. [Switching to Thread -1226869056 (LWP 7449)] 0xffffe410 in __kernel_vsyscall () (gdb) thread apply all bt
+ Trace 66698
Thread 1 (Thread -1226869056 (LWP 7449))
*** Bug 334580 has been marked as a duplicate of this bug. ***
Created attachment 61443 [details] [review] patch I have seen this too. This patch should fix the memory corruption (at least the one I experienced): GconfValue should be freed with gconf_value_free not with g_free. The patch also fixes a tiny leak in another part of the code that I noticed while running valgrind to detect the memory corruption.
Paolo, thank you very much for the Patch. Fixed on HEAD: 2006-03-20 Fernando Herrera <fherrera@onirica.com> * src/gconf-editor-window.c: (gconf_editor_gconf_value_changed): Fix memory corruption. GconfValue should be freed with gconf_value_free not with g_free. * src/gconf-list-model.c: (gconf_list_model_notify_func): Fix a tiny leak. Patch from Paolo Borelli. Closes bug #332931.
*** Bug 335176 has been marked as a duplicate of this bug. ***
Can this patch be applied to the 2.14 branch too, please?
I have not yes branched gconf-editor for gnome-2-14. I'll branch it after 2.14.1, so the fix will be on 2.14 and 2.15
*** Bug 335807 has been marked as a duplicate of this bug. ***
*** Bug 338157 has been marked as a duplicate of this bug. ***