GNOME Bugzilla – Bug 106758
Crash in Red Hat beta (old vfolder backend)
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-vfs Severity: normal Version: 2.2.1 Synopsis: Crash in Red Hat beta (old vfolder backend) Bugzilla-Product: gnome-vfs Bugzilla-Component: Other BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Filing this for own reference, doesn't really apply to GNOME 2.2 Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found)...[New Thread 1087974208 (LWP 7757)] [New Thread 1150495424 (LWP 7773)] [New Thread 1142106944 (LWP 7772)] [New Thread 1133718464 (LWP 7771)] [New Thread 1125329984 (LWP 7770)] [New Thread 1116941504 (LWP 7768)] [New Thread 1099771200 (LWP 7767)] 0xffffe002 in ?? ()
+ Trace 34121
Thread 1 (Thread 1087974208 (LWP 7757))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-21 16:38 ------- Reassigning to the default owner of the component, gnome-vfs-maint@bugzilla.gnome.org.
See also https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=84668
*** Bug 106760 has been marked as a duplicate of this bug. ***
Bug 106760 trace may have slightly more symbols.
I believe this was caused by a race in gnome-vfs-monitor.c. I think it is fixed by this checkin: 2003-02-24 Alexander Larsson <alexl@redhat.com> * libgnomevfs/gnome-vfs-monitor.c (destroy_monitor_handle): Warn if the handle was not in the hash table. (gnome_vfs_monitor_callback): Loop to get the hashtable. This fixes a possible race where there is a callback before the add_monitor code has added the monitor to the hashtable. (#106758) Reopen this if anyone still see this with that fix.
*** Bug 114569 has been marked as a duplicate of this bug. ***