From: GStreamer (bugzilla.gnome.o. <bug...@gn...> - 2010-02-03 19:43:22
|
https://bugzilla.gnome.org/show_bug.cgi?id=608901 GStreamer | gst-plugins-base | 0.10.25 --- Comment #1 from tia...@gm... 2010-02-03 19:43:07 UTC --- Created an attachment (id=152959) --> (https://bugzilla.gnome.org/attachment.cgi?id=152959) pure gnomevfs crash test i did some debugging (with some help at work) and we find out that the problem is at the method "gst_gnome_vfs_src_get_size". The method uses some info facilities of gnomevfs. We started to test gnomevfs alone and we where able to determine that when you just open and read the same ssh uri multiple times on multiple threads, it works fine. But if you try to read and access the info of the same ssh uri from multiple threads, it crashes. The main difference is that sometimes it crashes like gstreamer and sometimes a deadlock happens (if you start something like 30 worker threads it always give a GLib-ERROR **: /build/buildd/glib2.0-2.22.3/glib/gmem.c:175: failed to allocate [lot of] bytes), and a lot of protocol errors and i/o errors gets printed. It looks that gnomevfs has a problem with thread safety when you require info about the same ssh uri from multiple threads (other protocols looks to work fine). Source code without info that works fine: https://svn.inf.ufsc.br/katcipis/c/gnomevfs_bug/ok_test.c Source code with info that crashes: https://svn.inf.ufsc.br/katcipis/c/gnomevfs_bug/crash_test.c Source code with info and with mutex that works fine: https://svn.inf.ufsc.br/katcipis/c/gnomevfs_bug/ok_mutex_test.c -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |