Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gst-plugins-bad
gst-plugins-bad
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,024
    • Issues 1,024
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 201
    • Merge Requests 201
  • 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
  • gst-plugins-badgst-plugins-bad
  • Issues
  • #1530

Closed
Open
Created Feb 17, 2021 by Víctor Manuel Jáquez Leal@vjaquezMaintainer

va: investigate a way to dismiss unused memories after reverse playback

While reverse playback the number of buffer has to increase since the whole GOP has to be allocated before rendering. This might bring a lot of memory pressure, mainly in hardware accelerated decoding.

For example, in order to make more efficient the dmabuf-based memory allocation, va has an allocator's pool that stores all the created and released memories. But, after reverse playback (returning to normal playback) a lot of memories aren't required any more. It should be nice to find a mechanism to invalidate that memory cache.

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