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 973
    • Issues 973
    • 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
  • #812
Closed
Open
Issue created Nov 02, 2018 by Bugzilla Migration User@bugzilla-migration

codecparsers_h26x: Should return NO_NAL_END on 5/6 bytes NALs

Submitted by Nicolas Dufresne @ndufresne

Link to original bug (#797371)

Description

-- regression introduce by https://bugzilla.gnome.org/show_bug.cgi?id=732553 ---

If you pass any valid 5 first bytes of a NAL to the parser, it will now always return OK instead of NO_NAL_END. This is caused by broken code trying to handle single byte SEQ_END / STREAM_END as being complete NAL.

Assignee
Assign to
Time tracking