GNOME Bugzilla – Bug 536432
crash in Document Viewer:
Last modified: 2008-06-10 08:19:57 UTC
Version: 2.22.1.1 What were you doing when the application crashed? Distribution: Fedora release 9 (Sulphur) Gnome Release: 2.22.1 2008-05-07 (Red Hat, Inc) BugBuddy Version: 2.22.0 System: Linux 2.6.25.3-18.fc9.i686 #1 SMP Tue May 13 05:38:53 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10499901 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 80646144 vsize: 80646144 resident: 35647488 share: 14131200 rss: 35647488 rss_rlim: 4294967295 CPU usage: start_time: 1212487762 rtime: 1646 utime: 1330 stime: 316 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evince' [Thread debugging using libthread_db enabled] [New Thread 0xb8095730 (LWP 10713)] [New Thread 0xb7c69b90 (LWP 10714)] 0x00110416 in __kernel_vsyscall ()
+ Trace 199487
Thread 2 (Thread 0xb7c69b90 (LWP 10714))
----------- .xsession-errors --------------------- (gsf-office-thumbnailer:20740): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed calling convert '/tmp/.gnome_thumbnail.44YECU.EB06BU' +matte -thumbnail 128x128 png:'/tmp/.gnome_thumbnail.44YECU' (gsf-office-thumbnailer:21105): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed camel-Message: -- (evolution:3441): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed (evolution:3441): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed ** (inkscape:12432): CRITICAL **: SPObject* sp_object_unref(SPObject*, SPObject*): assertion `object != NULL' failed Cannot access memory at address 0xd Could not find the frame base for "ev_document_render". Cannot access memory at address 0xd --------------------------------------------------
That's my first time using bug-buddy. I'm not sure what information that the stack-trace provides. At the time of the crash (and it's happened several times) I was going through my standard edit->pdflatex->view cycle. It's possible that the changes from the pdflatex compilation hadn't been fsynced to the disk (or something) as I hit Ctrl+R quite quickly after I see the compilation complete. Anyway, I didn't think the stack-trace would go straight to bugzilla. I thought there'd be some pre-filtering against well-known stack traces.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 536482 ***