[Gtk2-perl-bugs] [Bug 620099] Make it safe to call into Glib from foreign threads

[gnome-perl (bugzilla.gnome.o. <bug...@gn...>]

https://bugzilla.gnome.org/show_bug.cgi?id=620099
  gnome-perl | Glib | unspecified

Quentin Sculo <squentin> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |squ...@fr...

--- Comment #8 from Quentin Sculo <squ...@fr...> 2011-05-18 20:07:43 UTC ---
Thanks a lot.
I did only a few tests so far, but it seems good enough for using playbin2 and
the about_to_finish signal in my app.

I did a few quick tests with other sources of crashes related to gstreamer, and
it is much better, for example, computing replaygain info in my app using the
gstreamer plugin was extremely unstable before, with this patch it looks very
stable.

I also tested connecting to the notify signal of the playbin2 gstreamer element
to get a signal when its volume property change (the volume of the playbin2
element is linked to the master volume when using pulseaudio), and though a
simple callback as {warn "@_"} seems to work (it crashes when changing the
volume without the patch), a more elaborate callback such as :
 my ($object,$property)=@_;
 my $name=$property->get_name;
 warn "$object property $name changed : ".$object->get($name)."\n";
causes the app to hang when it starts playing (it crashes without the patch)
after printing a few "property changed" messages, it ends with the "*** GPerl
asked to invoke callback from another thread, handing callback over to the main
loop" message from the patch.

I also got at least 2 similar hanging while testing the visual gstreamer plugin
(plugin that does some drawing with the music)

So it is a great improvement, though it seems there is still some cases where
it will hang. I don't know if it is possible to fix that, but even as is I hope
it will be committed soon.

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