[gstreamer-bugs] [Bug 349410] Problems with type handling

[GStreamer (bugzilla.gnome.org)]

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:
  http://bugzilla.gnome.org/show_bug.cgi?id=349410

  GStreamer | gstreamer (core) | Ver: HEAD CVS




------- Comment #37 from Antoine Tremblay  2008-01-10 19:26 UTC -------
>That's just for the GType registration, I think (which we've been doing from a
>thread-safe context for a long time).

It's for GType registrations yes,, but not everything was in a thread-safe
context.. Most basic types of gstreamer are but for example everything that is
in a plugin is not, and I think there's still some basic types in the base libs
that are not...

First thing would be to have this in the BOILERPLATE 

>I don't think it will happen with these changes. Why do you think it will?

It will.. I tested a lot and it could really happen anywhere.. granted the
basic types were the most common issue but it can happen really anywhere
especially in the plugin inits... so the boilerplate should include this for
sure. 

I'm just not sure how to add _once _leave to keep compatitiblity with earlyer
versions of Glib.. maybe with a __weak__ symlink... or checking with pkg-config
and enabling the correct code...


-- 
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=349410.