GNOME Bugzilla – Bug 496596
crash in Open Folder: The file browser crashed...
Last modified: 2007-11-17 19:33:08 UTC
Version: 2.18.3 What were you doing when the application crashed? The file browser crashed when accessing the properties of a folder with 1354 items in it taking up 584.8 MB. It has been crashing more often since I tried to view the properties info for a folder with a large number of items ~ 150000; taking up ~90GB. Hope this helps. Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 356110336 vsize: 356110336 resident: 39870464 share: 15302656 rss: 39870464 rss_rlim: 18446744073709551615 CPU usage: start_time: 1194996855 rtime: 2397 utime: 1888 stime: 509 cutime:0 cstime: 0 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 0x2b3f4de58bc0 (LWP 9846)] [New Thread 0x43005950 (LWP 10151)] (no debugging symbols found) 0x00002b3f474e6c7f in waitpid () from /lib/libpthread.so.0
+ Trace 177548
Thread 1 (Thread 0x2b3f4de58bc0 (LWP 9846))
----------- .xsession-errors (43 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui. More details can be found here: http://live.gnome.org/GettingTraces
Hello! Thank you for your work on making such good packages! I've installed the package gnome-dbg and have recreated the failure. I am seeking to view the properties of a file contained on an external hard drive. Here is the output from bug buddy: Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 341716992 vsize: 341716992 resident: 27160576 share: 15097856 rss: 27160576 rss_rlim: 18446744073709551615 CPU usage: start_time: 1195228763 rtime: 1311 utime: 262 stime: 1049 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0x2acf703e8bc0 (LWP 5060)] 0x00002acf69a76c7f in waitpid () from /lib/libpthread.so.0
+ Trace 178195
Thread 1 (Thread 0x2acf703e8bc0 (LWP 5060))
----------- .xsession-errors --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 warning: .dynamic section for "/usr/lib/libgnomecanvas-2.so.0" is not at the expected address (wrong library or version mismatch?) -------------------------------------------------- (In reply to comment #1) > Thanks for taking the time to report this bug. > Unfortunately, the stack trace is missing some elements that will help a lot to > solve the problem, so it will be hard for the developers to fix that crash. > > Could you please help fixing this by installing some debugging packages [1], > start the application as normal, and try to reproduce the crash, if possible? > > Once bug-buddy pops up, you can find the stacktrace in the 'Details', now > containing way more information. Please copy that stacktrace and paste it as a > comment here. Thanks in advance! > > [1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, > libgnome, and libgnomeui. > > More details can be found here: http://live.gnome.org/GettingTraces >
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 in version 2.20. It should be solved in the next software version. You may want to check for a software upgrade, or ask Debian for a fix for version 2.18. *** This bug has been marked as a duplicate of 355018 ***