[gstreamer-bugs] [Bug 420106] totem crashed with SIGSEGV in resample_set_format()
bugzilla-daemon at bugzilla.gnome.org
Fri Mar 30 02:09:39 PDT 2007
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
GStreamer | gst-plugins-base | Ver: 0.10.12
------- Comment #2 from Tim-Philipp Müller 2007-03-30 09:07 UTC -------
> http://librarian.launchpad.net/6995855/%3Cfdopen%3E has a similar backtrace
> coming from rhythmbox.
Very useful, thanks!
So, I wonder if the following race(?) could happen when a
GstBaseTransform-based element's state goes from PAUSED => READY:
Streaming-Thread: in gst_pad_chain_unchecked():
- take STREAM_LOCK
- take OBJECT_LOCK
- check if pad is flushing
- release OBJECT_LOCK
Shutdown-Thread: in gst_pad_activate_push(FALSE):
- take OBJECT_LOCK (in pre_activate)
- set pad to flushing (in pre_activate)
- release OBJECT_LOCK (in pre_activate)
- call GST_PAD_ACTIVATEPUSHFUNC(), which was
set by GstBaseTransform and which will call
GstBaseTransform::stop() where elements
might clear all their state.
Streaming-Thread: still in gst_pad_chain_unchecked():
- call gst_pad_configure_sink() which will/might cause
GstBaseTransform::set_caps() to be called, which
elements will only expect after they have been
started again and their state has been initialised
Or am I missing anything here? If not, core bug, basetransform bug or element
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=420106.
More information about the Gstreamer-bugs