GNOME Bugzilla – Bug 302735
crash while cancelling a 'rename' over ssh://
Last modified: 2006-03-18 11:50:52 UTC
Distribution: Debian 3.1 Package: nautilus Severity: normal Version: GNOME2.10.0 2.10.0 Gnome-Distributor: Ubuntu Synopsis: crash while cancelling a 'rename' over ssh:// Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.10.0 BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Nautilus craches sometimes when i cancel a rename (rename directory) over ssh://very.slow.server Steps to reproduce the crash: 1. open ssh://very.slow.server/ 2. right-click on the TO_RENAME Folder then select 'rename' 3. a popup happends to ask for cancel during the operation 4. pressing 'cancel' crashes Nautilus Expected Results: 4. pressing cancel should give up the renaming and not crash Nautilus How often does this happen? 30% Additional Information: gnome 2.10 ubuntu hoary Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1223899904 (LWP 8238)] [New Thread -1248855120 (LWP 21055)] [New Thread -1248588880 (LWP 21054)] [New Thread -1248035920 (LWP 21014)] [New Thread -1236477008 (LWP 8269)] [New Thread -1236210768 (LWP 8268)] [New Thread -1235944528 (LWP 8267)] [New Thread -1235280976 (LWP 8266)] [New Thread -1225847888 (LWP 8252)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 59052
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-05-02 16:11 UTC ------- Unknown version 2.10.0 in product nautilus. Setting version to "2.10.x". The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was brouits@free.fr.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
I was able to reproduce this bug sometime back with 'smb', with 2.6 version of nautilus and gnome-vfs. As i remember, funtion eel/eel-stock-dialog.c (timed_wait_free) is being called twice. Once from, cancel_rename_callback->cancel_rename->eel_timed_wait_stop->timed_wait_free. And second call from, timed_wait_dialog_destroy_callback->timed_wait_free. Second will assert and lead to crash. Since the code for this cancel operation is not much changed, looks like bug is still vaild for current soruces. Not sure though. I'm pasting the stack trace (nautilus 2.6, gnome-vfs 2.6), hope it helps.
+ Trace 59383
Re-opening the bug atm.
According to simple-dup-finder this is a duplicate of bug 91468, but since that was closed without a resolution I don't want to mark this as a duplicate.
Nice info here, confirming.
The problem is probably that a delayed close (timed_wait_delayed_close_timeout_callback) was already launched and the user pressed cancel afterwards, so both handlers ran.
Created attachment 57221 [details] [review] Possible fix I think this patch might fix it. Anyone want to verify it?
I'm pretty sure this is right, so I'm commiting it. I'd still like someone to verify it though.
No response, marking as FIXED.