GNOME Bugzilla – Bug 391318
crash in Text Editor: Openning 16MB text file ...
Last modified: 2006-12-31 16:37:24 UTC
Version: 2.15.9 What were you doing when the application crashed? Openning 16MB text file from CD-ROM Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2868.fc6 #1 SMP Fri Dec 15 17:29:48 EST 2006 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Permissive Accessibility: Enabled ----------- .xsession-errors --------------------- (nautilus:3750): Gtk-CRITICAL **: gtk_tree_path_compare: assertion `b->depth > 0' failed (nautilus:3750): Gtk-CRITICAL **: gtk_tree_path_compare: assertion `b->depth > 0' failed GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized ** (bug-buddy:4571): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 380399616 vsize: 380399616 resident: 16306176 share: 11997184 rss: 16306176 rss_rlim: -1 CPU usage: start_time: 1167577587 rtime: 42 utime: 37 stime: 5 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496355088 (LWP 4552)] (no debugging symbols found) 0x0000003bce80d935 in waitpid () from /lib64/libpthread.so.0
+ Trace 98288
Thread 1 (Thread 46912496355088 (LWP 4552))
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 354046 ***