Incorrect use of g_free instead of g_object_unref
Bug #36643 reported by
Sylvain Defresne
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gconf-editor (Ubuntu) |
New
|
Medium
|
Unassigned | ||
Bug 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=
[1] http://
To post a comment you must log in.
