GNOME Bugzilla – Bug 767892
item-manager: Fix the lifetime of the changes-pending handler
Last modified: 2016-06-22 10:26:13 UTC
After upgrading to GNOME 3.20 on Ubuntu GNOME 16.04 I have found that it is reported to me randomly that gnome-photos has crashed even though I have not launched gnome-photos in the current session (it seems that it is always running in the background). So it seems to just randomly crash and exit in the background. The error message I am provided with is: gnome-photos crashed with SIGABRT in g_assertion_message() This issues was already filed downstream by somebody else: https://bugs.launchpad.net/ubuntu-gnome/+bug/1568043 But I thought that as I couldn't find any reports upstream on the issue that I should file one here.
Here is a stack trace from the downstream bug: https://launchpadlibrarian.net/252885058/StacktraceSource.txt Since you haven't explicitly started the application, it sounds like it is the gnome-shell search provider that is crashing. I am curious if the PhotosItemManager instance is getting destroyed (ie. photos_item_manager_dispose is being called) while it is still being used. You can set it up as: $ gdb /usr/bin/gnome-photos $ break photos_item_manager_dispose $ run --gapplication-service And then go the gnome-shell overview and type something. When it crashes it will also be interesting to look at the value of self->priv->objects in photos_base_manager_get_object_by_id. If PhotosItemManager has already been destroyed, it will be NULL.
Created attachment 330146 [details] [review] item-manager: Fix the lifetime of the changes-pending handler Does this help? Can you try running with this patch and see if it still crashes the same way or not?
Comment on attachment 330146 [details] [review] item-manager: Fix the lifetime of the changes-pending handler Pushed to master and gnome-3-20.