Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-daemon
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 111
    • Issues 111
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-daemon
  • Issues
  • #626

Closed (moved)
(moved)
Open
Created Sep 09, 2021 by Sébastien Blin@sblinOwner

Mediademuxer: buffer can increase

In MediaDemuxer::decode():

av_read_frame only return one frame of the video buffer. However, if the CPU is too slow to decode (should not happen, but still), frames can just be stored and the video buffer can increase with a big maximum.

This should never happen. If the video buffer gets too big, the video will have a big delay.

But we also should not hide other problems. So, potential solution:

Check the size of the internal video buffer and log if too big before flushing.

Assignee
Assign to
Time tracking