GNOME Bugzilla – Bug 408293
crash in Home Folder:
Last modified: 2007-03-13 19:32:23 UTC
What were you doing when the application crashed? Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.19-1.2911.fc6 #1 SMP Sat Feb 10 15:16:31 EST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 542732288 vsize: 542732288 resident: 42045440 share: 20504576 rss: 42045440 rss_rlim: -1 CPU usage: start_time: 1171523169 rtime: 6342 utime: 5080 stime: 1262 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 46912496347056 (LWP 3218)] 0x0000003aa120d96f in waitpid () from /lib64/libpthread.so.0
+ Trace 111016
Thread 1 (Thread 46912496347056 (LWP 3218))
Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug. Also, 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 also installing glib2-debuginfo and gtk2-debuginfo, 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! More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 408312 has been marked as a duplicate of this bug. ***
*** Bug 408319 has been marked as a duplicate of this bug. ***
*** Bug 408374 has been marked as a duplicate of this bug. ***
from bug 408858:
+ Trace 111478
*** Bug 408858 has been marked as a duplicate of this bug. ***
*** Bug 409572 has been marked as a duplicate of this bug. ***
As I have pointed out early, I have ssh access to this guy's machine and tried to do some debugging today, despite my complete ignorance in GNOME internals :) I'm attaching a short extract from my debugging session with some interesting moments marked with ####. Resume: as far as I understand, update_menus_timeout_callback (and perhaps other callbacks - I've seen similar things in linked bug reports - for example, see bug #408293 where fm_directory_view_update_menus is the timer callback that caused the crash) is called regularily on some timeout (perhaps even asynchronously?). If you happen to click the close button just a bit before the callback is called, nautilus crashes because some fields in callback data were already NULLed out. I think the solution is to cancel the timer callback before the windows starts to be destroyed.
Created attachment 82905 [details] A extract from gdb session
*** Bug 410440 has been marked as a duplicate of this bug. ***
*** Bug 412557 has been marked as a duplicate of this bug. ***
*** Bug 413518 has been marked as a duplicate of this bug. ***
*** Bug 416146 has been marked as a duplicate of this bug. ***
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 349551 ***