[Bug 36643] Incorrect use of g_free instead of g_object_unref

[Sylvain Defresne]

Public bug reported:
https://launchpad.net/malone/bugs/36643

Affects: gconf-editor (Ubuntu)
       Severity: Normal
       Priority: (none set)
         Status: Unconfirmed

Description:
When using gconf-editor to change a key, I get the following warning on
the console. If I try to use the application after that it crash.

$ gconf-editor
*** glibc detected *** double free or corruption (out): 0x082c0540 ***

The following recent thread on debian-devel [1] implies that it is
caused by an application bug incorrectly using g_free instead of
g_object_unref to release object. It worked previously as memory for
objects was allocated using g_malloc, but with many objects switching to
g_slice_alloc this does not work any longer.

The workaround of running gconf-editor with G_SLICE=always-malloc works,
which seems to confirm this bug.

[1] http://lists.debian.org/debian-devel/2006/03/msg00941.html