GNOME Bugzilla – Bug 576731
gvfsd-trash crashed with SIGSEGV in g_simple_async_result_complete()
Last modified: 2013-11-04 08:47:29 UTC
this report has been filed here: https://bugs.edge.launchpad.net/ubuntu/+source/gvfs/+bug/345754 "When i empty the trash it crashed." ".
+ Trace 213845
Thread 1 (process 3923)
seems to still be an issue and not distro specific, see https://bugzilla.redhat.com/show_bug.cgi?id=612698
is there any required info in order to fix this bug? it is still an issue with 2.32.
This still happens with the current git master of gvfs. To reproduce: - Get a Totem with that patch: http://git.gnome.org/browse/totem/commit/?id=8ef36a2c74f1b9e614b7f94b8a53d4190c3bbebd (not required, but it makes reproducing the bug a doodle) - Make sure your copy of GStreamer ships with a giosrc plugin: giosrc - Start playing a video file from the trash, and seek around it in Totem
+ Trace 229443
*** Bug 651748 has been marked as a duplicate of this bug. ***
So a naive solution is to just guard the crashing line with "if (job)". But in looking at the code, I'm curious why the write async calls don't have cancellables or data structures like the read async calls do. And how likely it is that we'd have multiple write calls extant? (g_vfs_channel_send_reply doesn't guard against being called multiple times, and it seems plausible to me that it would be, but I don't grok the gvfs code paths)
This is not reproducible on current git master so it must have been fixed up in the meantime.