Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-plugins-rs gst-plugins-rs
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 69
    • Issues 69
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 21
    • Merge requests 21
  • 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-rsgst-plugins-rs
  • Issues
  • #93

Closed
Open
Created Jan 17, 2020 by Mathieu Duponchelle@meh🐸Maintainer

threadshare: block_on panics because it is running in a Context

I have been trying to fix this on my end but my brain isn't working anymore :(

Consider the following pipeline:

gst-launch-1.0 audiotestsrc ! alawenc ! rtppcmapay ! ts-jitterbuffer ! rtppcmadepay ! alawdec ! fakesink

This is a simplified scenario, my actual use case has a sender and receiver pipeline, but it can be reproduced with this single pipeline too.

stack.txt

Here, audiodecoder (from its streaming thread) constructs and sends a latency query upstream (frame 30). The jitterbuffer receives it and attempts to block_on in its src_query handler, which panics as it is indeed running in its own context (see the pop_and_push at frame 55).

I don't know how to fix this :)

Edited Jan 17, 2020 by Mathieu Duponchelle
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking