Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • mesa mesa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3,059
    • Issues 3,059
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 997
    • Merge requests 997
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • MesaMesa
  • mesamesa
  • Issues
  • #45
Closed
Open
Issue created Sep 18, 2019 by Bugzilla Migration User@bugzilla-migration

DispatchList leaked in glxapi.c?

Submitted by Andy Skinner

Assigned to mes..@..op.org

Link to original bug (#64335)

Description

get_dispatch() in glxapi.c grows the DispatchList table. It is small, but as far as I can see, items don't get removed as a Display is closed.

Could/should this get cleaned up, maybe from close_display_callback() in fakeglx.c?

It is a small leak (we see 24 bytes per Display in 7.2), but I think it would be better if closed, as this list will just grow. I don't know if the table pointed to by the structures in this list are cleared up, but I haven't seen them as leaks.

The relevant code looks similar in repository.

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