GNOME Bugzilla – Bug 602678
crash in Document Viewer: Opening a very, very lar...
Last modified: 2009-11-23 05:04:13 UTC
Version: 2.26.2 What were you doing when the application crashed? Opening a very, very large one-page pdf containing a rail map. Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-10-27 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.30-2-686 #1 SMP Sat Sep 26 01:16:22 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: gnome-alternative GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 67710976 vsize: 67710976 resident: 14630912 share: 11702272 rss: 14630912 rss_rlim: 18446744073709551615 CPU usage: start_time: 1258933689 rtime: 34 utime: 30 stime: 4 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 0xb5058b70 (LWP 10847)] [New Thread 0xb5951b70 (LWP 10846)] 0xb8035424 in __kernel_vsyscall ()
+ Trace 219234
Thread 3 (Thread 0xb5951b70 (LWP 10846))
A debugging session is active. Inferior 1 [process 10845] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (194245 sec old) --------------------- (firefox-bin:2852): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:2852): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:2852): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:2852): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:2852): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:2852): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:2852): Gdk-WARNING **: XID collision, trouble ahead ...Too much output, ignoring rest... --------------------------------------------------
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 bug 567038 ***