GNOME Bugzilla – Bug 621905
Should assume a reference to the object when asynchronously getting the dbus connection
Last modified: 2010-06-17 16:51:14 UTC
GDBusProxy should assume a reference to the object when it asynchronously initializes itself, as g_async_initable_new_valist_async() drops the reference it gives to g_async_initable_init_async() just after the call 332 g_async_initable_init_async (G_ASYNC_INITABLE (obj), 333 io_priority, cancellable, 334 callback, user_data); 335 g_object_unref (obj); /* Passed ownership to async call */ The result is that e.g. nautilus segfaults like this (gdb) bt
+ Trace 222461
Created attachment 163934 [details] [review] patch
Looks good to me with two stylistic simple fixes - please include the bug number in the Subject line e.g. like this "Bug 621905 –" (notice the wider dash). Also, no trailing dot in the commit message and please keep it under chars 72); and - please include the bug url in the Body since that will make it easier for future archaeologist to figure out what's going on. Thanks!
Thanks, pushed to master with this commit message. commit b3cc28bc34bd0b341f1786dc478cff259ce5d1da Author: Cosimo Cecchi <cosimoc@gnome.org> Date: Thu Jun 17 18:26:15 2010 +0200 Bug 621905 – Assume a ref when doing async work When asynchronously acquiring the DBus connection, assume a reference to the proxy object, to avoid destroying it in the middle of the operation. See https://bugzilla.gnome.org/show_bug.cgi?id=621905