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

Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.

  • GStreamerGStreamer
  • gst-plugins-badgst-plugins-bad
  • Issues
  • #1141
Closed
Open
Issue created Dec 10, 2019 by Nazar Mokrynskyi@nazar-pc

webrtcbin: Is there a way to identify that WebRTC connection is closed?

From documentation at least there doesn't seem to be a clear way to catch an event of a remote client closing/dropping WebRTC connection. Is it true? If so, then it is hard to imagine WebRTC implementation being usable in practice.

UPD: Sad part if that it causes problems that shouldn't exist in Rust. With pipeline that has webrtcbin -> decodebin -> autoaudiosink for audio part it fails like this:

0:00:50.850212965 16200 0x7f6874001c70 WARN                   pulse pulsesink.c:702:gst_pulsering_stream_underflow_cb:<autoaudiosink0-actual-sink-pulse> Got underflow
fish: “env GST_DEBUG=3 cargo run” terminated by signal SIGSEGV (Address boundary error)
Exit code 139
Edited Dec 10, 2019 by Nazar Mokrynskyi
Assignee
Assign to
Time tracking