Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • dav1d dav1d
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 20
    • Issues 20
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VideoLAN
  • dav1ddav1d
  • Issues
  • #253

Closed
Open
Created Feb 21, 2019 by Thomas Davies@tj_davies

Support alternative memory managers and deprecate direct calls to malloc/free

There are a handful of places where malloc and free (and related calls like realloc) are called directly to allocate memory. It would be preferable if these calls could be abstracted and alternative memory managers could be used.

Some systems pre-allocate memory in a pool to reduce allocation costs, or impose a sandbox, and use their own memory management - and in these cases calling malloc directly could cause a crash. On Windows malloc can also be slow, and there are better managers around.

It would be better to abstract these calls through function pointers, or at least use macros defined in a header so all calls could be replaced in different applications

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking

VideoLAN code repository instance