GNOME Bugzilla – Bug 319873
[gnomevfssrc] lockup if ctrl-c is pressed at just the right time
Last modified: 2006-10-22 12:14:30 UTC
here's a backtrace of gst-launch gnomevfssrc ! decodebin ! xvimagesink, only one thread:
+ Trace 63731
not really sure what's going on here tho. just noting the bug.
actually i'm seeing this without ctrl-c, renaming the bug. with this pipeline: gst-launch gnomevfssrc location=http://localhost:8800/ ! decodebin ! xvimagesink something is broadcasting on 8800, but it could be that no data is coming out...
This can only be made to work if we use async gnomevfs handling and gnomevfssrc returns ASYNC from the state change to PAUSED. Is this worth it?
(In reply to comment #2) > Is this worth it? Yes, definitely, it causes problems in apps like rhythmbox, see bug #313049 comment #76.
A simple alternative would be to do nothing in the _start method, but to open the connection right before producing data in the streaming thread. the pipeline will appear to not complete the state change to PAUSED (as is now) but the application will be able to cancel the operation.
This is closely related or even identical to bug #338827 (posted patch there), maybe either should be closed to keep the discussion central.
(In reply to comment #5) > This is closely related or even identical to bug #338827 (posted patch there), > maybe either should be closed to keep the discussion central. Yep, this bug should be closed as a duplicate of bug #338827. If there are no objections, I'll do it.
*** This bug has been marked as a duplicate of 338827 ***