Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gstreamer gstreamer
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 923
    • Issues 923
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 436
    • Merge requests 436
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamerGStreamer
  • gstreamergstreamer
  • Issues
  • #274
Closed
Open
Issue created Feb 06, 2018 by Bugzilla Migration User@bugzilla-migration

blocking probe and flush events issue

Submitted by Patricia Muscalu

Link to original bug (#793213)

Description

Created attachment 367948
test application

The following problem has been observed:

a blocking probe (GST_PAD_PROBE_TYPE_BLOCK_DOWNSTREAM |
GST_PAD_PROBE_TYPE_DATA_DOWNSTREAM |
GST_PAD_PROBE_TYPE_EVENT_FLUSH)

is installed on the source pad. When the pad is blocked, a flushing seek is performed. No flush-start/flush-stop events are received in the probe.
Is the probe installed in an incorrect way?

The attached dummy test application exposes the problem.

Attachment 367948, "test application":
test-blocking-probe.c

Assignee
Assign to
Time tracking