GNOME Bugzilla – Bug 741934
Crash: assertion failed: (cairo_image_surface_get_format (surface) == CAIRO_FORMAT_RGB24 || cairo_image_surface_get_format (surface) == CAIRO_FORMAT_ARGB32)
Last modified: 2018-03-05 17:49:18 UTC
Created attachment 293309 [details] gdb backtrace Running Debian's shotwell 0.20.1-1, I there is some image in my library which, when I scroll to it in the preview pane, causes a crash. Logs attached
Created attachment 293310 [details] shotwell.log
I assume you don't know which image is causing this. Do you have any "odd" images in your library, like a TIFF or PNG? It could be a RAW image too. If you browse through ~/.cache/shotwell/thumbs/thumbs360 with Nautilus, the thumbnailer may not crash (although it might), but do you see a thumbnail it can't generate?
This same error occurs for me when I scroll through a large collection quickly (for instance holding Page-Down). I'm using Shotwell 0.20.2 on Arch. Scrolling through the suggested directory with Nautilus does not show a thumbnail which isn't visible. The full error for me is as follows (don't how to make a log): Could not make snapshot ** Gdk:ERROR:gdkcairo.c:193:gdk_cairo_surface_paint_pixbuf: assertion failed: (cairo_image_surface_get_format (surface) == CAIRO_FORMAT_RGB24 || cairo_image_surface_get_format (surface) == CAIRO_FORMAT_ARGB32) Aborted (core dumped) Incidentally, when I press End in a large folder (such as the Library), Shotwell crashes with the same error, but also many Gtk-WARNING errors with "out of memory", and sometimes the line "Could not get snapshot data buffer".
Jim I have tried to figure out which image is triggering this for me, without succeeding yet. In fact, I would swear that as I add more photos to my collection, the image that triggers it is changing, moving toward the beginning of the collection (possibly at the same rate as I add more images).
Have now updated to Debian's Shotwell 0.20.2-2+b1. I am still seeing catastrophic failures after scrolling a certain (possible fixed) distance into the Library, and into specific tag panes. If I scroll with mouse gestures, I can still reproduce the previous crash form: Gdk:ERROR:/build/gtk+3.0-5i5HPl/gtk+3.0-3.14.4/./gdk/gdkcairo.c:193:gdk_cairo_surface_paint_pixbuf: assertion failed: (cairo_image_surface_get_format (surface) == CAIRO_FORMAT_RGB24 || cairo_image_surface_get_format (surface) == CAIRO_FORMAT_ARGB32) Aborted If I scroll with pagedown or the side slider, I instead typically see the preview pane become blank, with some out-of-memory errors in the console. My system has at least 5GB of RAM free at that point, probably more if it swapped. Shotwell's VSZ is 1.7GB, RSS is 260MB. Can send an strace if it's useful; the console log is: ** (shotwell:20524): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. L 20524 2015-04-06 18:59:44 [CRT] Directory NikonPreview with 8224 entries considered invalid; not read. [SCROLLING HAPPENS HERE] (shotwell:20524): Gtk-WARNING **: drawing failure for widget `CheckerboardLayout': out of memory (shotwell:20524): Gtk-WARNING **: drawing failure for widget `GtkViewport': out of memory (shotwell:20524): Gtk-WARNING **: drawing failure for widget `LibraryMainPage': out of memory (shotwell:20524): Gtk-WARNING **: drawing failure for widget `GtkNotebook': out of memory (shotwell:20524): Gtk-WARNING **: drawing failure for widget `GtkBox': out of memory (shotwell:20524): Gtk-WARNING **: drawing failure for widget `GtkFrame': out of memory (shotwell:20524): Gtk-WARNING **: drawing failure for widget `GtkPaned': out of memory (shotwell:20524): Gtk-WARNING **: drawing failure for widget `GtkBox': out of memory (shotwell:20524): Gtk-WARNING **: drawing failure for widget `LibraryWindow': out of memory
Clarifying: tag panes seem to begin to trigger the crash once they have enough images in them, further suggesting that this not being caused by a specific corrupt image.
*** This bug has been marked as a duplicate of bug 786702 ***