After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 536432 - crash in Document Viewer:
crash in Document Viewer:
Status: RESOLVED DUPLICATE of bug 536482
Product: evince
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-03 13:54 UTC by aidan.delaney
Modified: 2008-06-10 08:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description aidan.delaney 2008-06-03 13:54:16 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 ()

Thread 2 (Thread 0xb7c69b90 (LWP 10714))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_spawn_sync
    from /lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 <signal handler called>
  • #9 FT_Done_Face
    from /usr/lib/libfreetype.so.6
  • #10 ??
    from /usr/lib/libpoppler-glib.so.3
  • #11 ??
    from /usr/lib/libcairo.so.2
  • #12 cairo_font_face_destroy
    from /usr/lib/libcairo.so.2
  • #13 ??
    from /usr/lib/libcairo.so.2
  • #14 ??
    from /usr/lib/libcairo.so.2
  • #15 ??
    from /usr/lib/libcairo.so.2
  • #16 cairo_scaled_font_destroy
    from /usr/lib/libcairo.so.2
  • #17 ??
    from /usr/lib/libcairo.so.2
  • #18 ??
    from /usr/lib/libcairo.so.2
  • #19 cairo_set_font_face
    from /usr/lib/libcairo.so.2
  • #20 CairoOutputDev::updateFont
    from /usr/lib/libpoppler-glib.so.3
  • #21 Gfx::opShowText
    from /usr/lib/libpoppler.so.3
  • #22 Gfx::execOp
    from /usr/lib/libpoppler.so.3
  • #23 Gfx::go
    from /usr/lib/libpoppler.so.3
  • #24 Gfx::display
    from /usr/lib/libpoppler.so.3
  • #25 Gfx::doForm1
    from /usr/lib/libpoppler.so.3
  • #26 Gfx::doForm
    from /usr/lib/libpoppler.so.3
  • #27 Gfx::opXObject
    from /usr/lib/libpoppler.so.3
  • #28 Gfx::execOp
    from /usr/lib/libpoppler.so.3
  • #29 Gfx::go
    from /usr/lib/libpoppler.so.3
  • #30 Gfx::display
    from /usr/lib/libpoppler.so.3
  • #31 Page::displaySlice
    from /usr/lib/libpoppler.so.3
  • #32 ??
    from /usr/lib/libpoppler-glib.so.3
  • #33 poppler_page_render
    from /usr/lib/libpoppler-glib.so.3
  • #34 pdf_document_render
    at ev-poppler.cc line 488
  • #35 ev_document_render
    at ev-document.c line 221
  • #36 ev_job_render_run
    at ev-jobs.c line 372
  • #37 handle_job
    at ev-job-queue.c line 137
  • #38 ev_render_thread
    at ev-job-queue.c line 264
  • #39 ??
    from /lib/libglib-2.0.so.0
  • #40 start_thread
    from /lib/libpthread.so.0
  • #41 clone
    from /lib/libc.so.6


----------- .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
--------------------------------------------------
Comment 1 Aidan Delaney 2008-06-03 13:58:16 UTC
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.
Comment 2 Cosimo Cecchi 2008-06-10 08:19:57 UTC
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 ***