GNOME Bugzilla – Bug 352576
crash on Document Viewer
Last modified: 2006-10-01 13:47:08 UTC
Version: 0.5.5 What were you doing when the application crashed? Exit evince after viewing the pdf https://compukid.no-ip.org/dev/papers/securing-httpd/securing-httpd.pdf Distribution: Debian 3.1 (sarge) Gnome Release: 2.15.91 2006-08-13 (GARNOME) BugBuddy Version: 2.15.90 Memory status: size: 164298752 vsize: 164298752 resident: 56815616 share: 12451840 rss: 56815616 rss_rlim: -1 CPU usage: start_time: 1156355475 rtime: 4441 utime: 3849 stime: 592 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/home/compukid/garnome/bin/evince' Using host libthread_db library "/lib/libthread_db.so.1". 0x00002b46840e37af in ?? ()
+ Trace 70879
Backtrace _does not_ seem to be generated from the listed binary. It was generated from /usr/bin/evice. Is this a bugbuddy bug? evince was executed from FireFox (src: garnome) /home/compukid/garnome/bin/evice is evice 0.5.5 from GARNOME 2.15.91 /usr/bin/evice is evice 0.4.0 from Debian unstable It does only happen with the old version.
The new version sometimes shows this string on the console with this document: *** glibc detected *** double free or corruption (!prev): 0x0000000000f6e860 ***
The old version shows this string before it crashes: Gtk-CRITICAL **: gtk_tree_model_foreach: assertion `GTK_IS_TREE_MODEL (model)' failed
Are you sure that 0.5.5 crashes this way? It reminds an old bug that should be fixed already. At least, can you provide better backtrace? See http://live.gnome.org/GettingTraces for more information on how to do so.
Created attachment 71485 [details] backtrace
> /tmp/evince/evince-0.4.0/debian/evince/usr/bin/evince Thanks, but it's a known bug that was fixed, what about 0.5.5?
Version 0.5.5 does not crash. It only shows the "double free or corruption" message.
Works for me, please upgrade your poppler
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 336825 ***