[gstreamer-bugs] [Bug 365501] [x/xvimagesink] race condition when creating first image buffer mini-object due to g_type_class_ref() not being thread-safe
GStreamer (bugzilla.gnome.org)
bugzilla-daemon at bugzilla.gnome.org
Fri Oct 27 05:00:27 PDT 2006
Do not reply to this via email (we are currently unable to handle email
responses and they get discarded). You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=365501
GStreamer | gst-plugins-base | Ver: HEAD CVS
Tim-Philipp Müller changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|totem-gstreamer- |gstreamer-
|maint at gnome.bugs |bugs at lists.sourceforge.net
Status|UNCONFIRMED |RESOLVED
Component|GStreamer backend |gst-plugins-base
Product|totem |GStreamer
QAContact|totem-gstreamer- |gstreamer-
|maint at gnome.bugs |bugs at lists.sourceforge.net
Resolution| |FIXED
Summary|crash in Movie Player: |[x/xvimagesink] race
| |condition when creating
| |first image buffer mini-
| |object due to
| |g_type_class_ref() not being
| |thread-safe
Target Milestone|--- |0.10.11
Version|2.16.x |HEAD CVS
------- Comment #1 from Tim-Philipp Müller 2006-10-27 11:59 UTC -------
Gah, I thought this was fixed ages ago. Looks like g_type_class_ref() isn't
entirely thread-safe either if the class doesn't exist yet. Should be fixed
now:
2006-10-27 Tim-Philipp Müller <tim at centricular dot net>
* sys/ximage/ximagesink.c: (gst_ximagesink_get_type):
* sys/xvimage/xvimagesink.c: (gst_xvimagesink_get_type):
Explicitly create our custom buffer classes at a thread-safe
location as well, since g_type_class_ref() doesn't seem to be
entirely thread-safe either (#365501; also see #349410).
--
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
More information about the Gstreamer-bugs
mailing list