Skip to content

GitLab

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

Closed
Open
Created Jan 13, 2017 by Bugzilla Migration User@bugzilla-migration

urisourcebin: Fix crash during EOS handling

Submitted by Seungha Yang

Link to original bug (#777212)

Description

Slot has two cases to receive fake EOS.
a) actual EOS from demuxer's pad
b) demuxer's pad-removed.
When a) happened, slot is still marked as linked.
And when b) happend, slot will be marked as unlinked.

Sometimes, following sequence is possible, and it causes crash

  • demuxer pushed EOS (fake-eos-A)
  • Then, the demuxer's pad was removed (fake-eos-A)
  • slot's srcpad got "fake-eos-A" but it was already marked as unlinked by
    pad-removed. So, urisourcebin will throw the slot to threadpool to remove it.
  • "fake-eos-B" reached to slot's src pad and trying to free the slot again.
Assignee
Assign to
Time tracking