Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • apk-tools apk-tools
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 94
    • Issues 94
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 19
    • Merge requests 19
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • alpinealpine
  • apk-toolsapk-tools
  • Issues
  • #10697
Closed
Open
Issue created May 17, 2020 by Rasmus Thomsen@Cogitri

Leaking memory in apk_atom_init

Hello,

in my D bindings for apk-tools I'm currently doing the following to open the database:

apk_atom_init();
apk_db_init(&this.db);

And the following to close the db:

if (this.db.open_complete)
{
    apk_db_close(&this.db);
}

This will happen a lot of times during the lifetime of my DBus server, since I try to avoid holding the lock on the database for too long, so users aren't blocked from using the apk CLI tool when the server isn't doing an operation. The problem is that apparently apk_atom_init leaks a sizeable amount of memory every time and I can't free it because that's behind an ifdef for valgrind - I guess exactly because it complains there.

Assignee
Assign to
Time tracking