Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • G GLib
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 880
    • Issues 880
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 47
    • Merge requests 47
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOME
  • GLib
  • Issues
  • #2057
Closed
Open
Created Mar 06, 2020 by Philip Withnall@pwithnall🚫Maintainer

Call malloc_trim() under memory pressure

@alexl pointed out this article about using malloc_trim() to release the memory which glibc holds on to on the assumption that there will be more malloc() calls soon (rather than releasing unused heap pages back to the kernel immediately).

We might want to consider calling it when under memory pressure, in the GMemoryMonitor code, if it’s available.

/cc @hadess

Assignee
Assign to
Time tracking