Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-plugins-good gst-plugins-good
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 648
    • Issues 648
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 82
    • Merge requests 82
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gst-plugins-goodgst-plugins-good
  • Issues
  • #607

Closed
Open
Created Jun 05, 2019 by Håvard Graff@hgrDeveloper

gstrtpjitterbuffer can deadlock

bf00ee46 introduced a deadlock. Basically, it is possible for gst_rtp_jitter_buffer_loop to end up in JBUF_WAIT_EVENT() inside the loop, while the _chain() function ends up in JBUF_WAIT_QUEUE(), and we are waiting forever.

I have yet to try and write a test for this, but architecturally I hope we could avoid having two threads waiting on each-other like that. (and a test to go with such a change to document what it is trying to do would not be a bad idea either) :)

Assignee
Assign to
Time tracking