Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • F ffmpeg-7.1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • sixue.cheng
  • ffmpeg-7.1
  • Repository

Switch branch/tag
  • ffmpeg-7.1
  • libavcodec
  • h264_parse.c
Find file BlameHistoryPermalink
  • Mark Wachsler's avatar
    libavcodec/h264_parse: don't use uninitialized value when chroma_format_idc==0 · 1df91b48
    Mark Wachsler authored Sep 07, 2017
    
    
    When parsing a monochrome file, chroma_log2_weight_denom was used without
    being initialized, which could lead to a bogus error message being printed, e.g.
      [h264 @ 0x61a000026480] chroma_log2_weight_denom 24576 is out of range
    It also could led to warnings using AddressSanitizer.
    Signed-off-by: default avatarMichael Niedermayer <michael@niedermayer.cc>
    (cherry picked from commit fde5c7dc
    
    )
    Signed-off-by: default avatarMichael Niedermayer <michael@niedermayer.cc>
    1df91b48

Replace h264_parse.c

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.