Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • gst-plugins-base gst-plugins-base
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 633
    • Issues 633
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 67
    • Merge requests 67
  • 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
  • gst-plugins-basegst-plugins-base
  • Issues
  • #280
Closed
Open
Issue created Aug 01, 2016 by Bugzilla Migration User@bugzilla-migration

appsink callback race condition

Submitted by Jake Foytik

Link to original bug (#769394)

Description

In gstappsink.c, it is possible to get undefined behavior if the gst_app_sink_set_callbacks() function is called while the element is in the PLAYING state and actively using the already set callbacks.

For example, it is possible for the gst_app_sink_set_callbacks() function to set callbacks.new_sample = NULL just after the gst_app_sink_render() function checks if callback.new_sample == NULL.

This can be prevented by adding a mutex around the usage of the callbacks and around the gst_app_sink_set_callbacks() function. Another option is to not allow the callbacks to be set if the element is in the PLAYING state.

Version: 1.8.0

Assignee
Assign to
Time tracking