GNOME Bugzilla – Bug 533523
crash in Open Folder:
Last modified: 2008-05-17 17:31:16 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-k7 #1 SMP Sun Feb 10 21:04:14 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 77643776 vsize: 77643776 resident: 24334336 share: 15499264 rss: 24334336 rss_rlim: 4294967295 CPU usage: start_time: 1211008549 rtime: 168 utime: 151 stime: 17 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6be4720 (LWP 18608)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 197936
Thread 1 (Thread 0xb6be4720 (LWP 18608))
----------- .xsession-errors (75201 sec old) --------------------- [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48] ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that 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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Added the -dbg info. Took a while to get it to crash again. I think this may be similar to 522534 except it is much more "resistant" to crashing now and doesn't appear to require the existence of a malformed 'thumbs.db' file. The first crash happened when I opened an VERY LARGE smb:// folder. After I had moved the complete folder to a local drive it opened fine. After installing the debugging symbols I tried to make it crash again and had to traverse several smb:// folders to make it happen. I do not see *ANY* commonalities between the two folders that caused it to crash. The second is quite small (only about 10 files) and none of the files are duplicates of what was in the other folder. Crash output from bug-buddy: Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-k7 #1 SMP Sun Feb 10 21:04:14 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 77713408 vsize: 77713408 resident: 25182208 share: 15495168 rss: 25182208 rss_rlim: 4294967295 CPU usage: start_time: 1211045154 rtime: 206 utime: 191 stime: 15 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/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6b5c720 (LWP 6169)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 197983
Thread 1 (Thread 0xb6b5c720 (LWP 6169))
----------- .xsession-errors (111781 sec old) --------------------- [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48]marker does not match f_code [mpeg4 @ 0xb67bfb48] ...Too much output, ignoring rest... --------------------------------------------------
absolutely a duplicate of bug 522534, thanks for the trace.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 522534 ***