Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gstreamer
gstreamer
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 422
    • Issues 422
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 82
    • Merge Requests 82
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gstreamergstreamer
  • Issues
  • #256

Closed
Open
Created Nov 16, 2017 by Bugzilla Migration User@bugzilla-migration

atomicqueue: not MT-safe and racy

Submitted by Matthew Waters @ystreet

Link to original bug (#790468)

Description

_push() and _pop() from different threads can result in skips and/or memory corruption.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None