abrt 1.0.3 detected a crash. How to reproduce ----- 1. N/A 2. N/A 3. N/A Comment: After rebooting and login, it has already been aborted. Attached file: backtrace cmdline: /usr/libexec/gvfsd-trash --spawner :1.7 /org/gtk/gvfs/exec_spaw/1 component: gvfs executable: /usr/libexec/gvfsd-trash kernel: 2.6.31.9-174.fc12.x86_64 package: gvfs-1.4.3-2.fc12 rating: 4 reason: Process was terminated by signal 6 (Aborted)
Created attachment 383671 [details] File: backtrace
Fixed upstream as: http://git.gnome.org/browse/gvfs/commit/?id=d618141ea5161d05e388e9fbfa4148a6abd976b1
According to comments in the upstream fix, the abort is due to a race condition having something to do with "freeing trash". The fix takes out the abort, and makes the comment that: "We just leak everything here, as this is not normally hit." Based on the number of hits being reported in the Fedora Bugzilla over the last few days, I would speculate that the "not normally hit" is false, and the upstream fix will introduce a "leak".
(In reply to comment #3) > ... I would speculate that the "not normally hit" is false, and > the upstream fix will introduce a "leak". It won't introduce a leak since the backend process will exit right away with a "Mountpoint Already registered" message. But yes, upstream developers were notified, that's TODO, to be 100% correct.
gvfs-1.4.3-3.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/gvfs-1.4.3-3.fc12
gvfs-1.4.3-3.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 566201 has been marked as a duplicate of this bug. ***