GNOME Bugzilla – Bug 498160
crash in Open Folder: searching for a file in ...
Last modified: 2007-11-20 19:48:42 UTC
Version: 2.18.3 What were you doing when the application crashed? searching for a file in a large multifolder Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Gorilla Memory status: size: 143826944 vsize: 143826944 resident: 56803328 share: 33525760 rss: 56803328 rss_rlim: 4294967295 CPU usage: start_time: 1195471224 rtime: 4844 utime: 3701 stime: 1143 cutime:4394 cstime: 1112 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208658208 (LWP 3635)] [New Thread -1210758256 (LWP 6017)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 178691
Thread 2 (Thread -1210758256 (LWP 6017))
----------- .xsession-errors (32 sec old) --------------------- Windows Media Video 9 decoder Windows Media Audio 8 decoder. Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error (199704): 3335 extraneous bytes after segment Out of memory --- Hash table keys for warning below: --> file:///home/cleaner (nautilus:5793): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:3635): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x2a392)! --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 454799 ***