[gstreamer-bugs] [Bug 565105] Gstreamer does not change from READY back to PAUSED in same cases

[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=565105

  GStreamer | gstreamer (core) | Ver: 0.10.19

Xabier Rodríguez Calvar changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |NEW




------- Comment #5 from Xabier Rodríguez Calvar  2008-12-23 15:15 UTC -------
(In reply to comment #4)
> when I removed the kill statement from the script to see where it hangs, it did
> not happen anymore. Any chance that the signal is just sent too quickly, before
> it can complete the state change?

I don't think so, because usually the complete and right execution
takes less than 6 seconds and the timeout is signal should kill the
program after 10 seconds. I think that margin should be enough to
change the state. But if you see the logs, when the signal is sent and
captured, it always is in the same state, waiting to come back from
READY to PAUSED. If you are not sure, you can use a longer timeout in
the script or remove it. I only wrote it to run the program in batch
because it would hang if I didn't add it.

So yes, you can remove it and run it to see the hang. It should
happen, I swear :-) .


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