Bug 782417 – inputselector: Need flush when set active pad and then seek in PAUSE state

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 782417 - inputselector: Need flush when set active pad and then seek in PAUSE state


Summary:	inputselector: Need flush when set active pad and then seek in PAUSE state


Status:	RESOLVED OBSOLETE

Product:	GStreamer
Classification:	Platform
Component:	gstreamer (core)
Version:	git master
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	git master
Assigned To:	GStreamer Maintainers
QA Contact:	GStreamer Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2017-05-10 03:33 UTC by kevin
Modified:	2018-11-03 12:40 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
inputselector: Need flush when set active pad and then seek in PAUSE state (2.47 KB, patch) 2017-05-10 03:38 UTC, kevin	none	Details \| Review

Description kevin 2017-05-10 03:33:00 UTC

Old will be blocked on gst_pad_push() when set active pad in PAUSE state. Need flush when set active pad and then seek in PAUSE state

Comment 1 kevin 2017-05-10 03:38:36 UTC

Created attachment 351504 [details] [review]
inputselector: Need flush when set active pad and then seek in PAUSE state

Comment 2 Tim-Philipp Müller 2017-12-24 17:04:37 UTC

Could you provide more context for this please, such as a stack trace of all threads. I'm not sure I understand the exact scenario here.

Comment 3 kevin 2017-12-25 07:48:31 UTC

I remember the pipeline will be blocked in the cases: pause -> active another video track -> seek.

Attached patch can fix the issue.

Comment 4 GStreamer system administrator 2018-11-03 12:40:59 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/234.