[Webkit-unassigned] [Bug 74986] GStreamer-WARNING **: wrong STREAM_LOCK count 0 after changing HTML5 video.src

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=74986





--- Comment #4 from Philippe Normand <pnormand at igalia.com>  2011-12-22 05:31:30 PST ---
(In reply to comment #3)
> Philippe,
> 
> So I'm just using PyGI to setup the Gtk Window and that sort of thing... PyGI isn't playing any part during the video playback, that's all JavaScript controlling it.
> 
> In terms of re-implementing my use-case in pure JavaScript... is it still okay if PyGI is what's doing the setup on the Gtk side of things?  Or what do you mean by that?
> 

Not sure. Is your code available online? Maybe I can have a look...

The "wrong STREAM_LOCK count 0" warning is emitted by GstTask. It seems the call to g_static_rec_mutex_unlock_full() returns 0, meaning that the stream lock wasn't first acquired in the calling thread.

It'd be interesting to know which element uses that GstTask, which thread acquires the lock and which one tries to release it.

Can you try to run your code in gdb like this?

G_DEBUG=fatal_criticals gdb -args /usr/bin/python ...

When the warning is emitted you could inspect the stack trace and the list of threads.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.