Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • campvis-public campvis-public
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

9.2.2023: Due to updates GitLab will be unavailable for some minutes between 9:00 and 11:00.

  • CAMP
  • campvis-publiccampvis-public
  • Issues
  • #9
Closed
Open
Issue created Jan 29, 2016 by Christian Schulte zu Berge@christian.szbContributor

GPU memory leak when multiple OpenGL contexts are active

As soon as they are multiple OpenGL contexts active at the same time, GPU memory leaks occur because some textures are not deleted correctly anymore.

According to early debugging sessions, glDeleteTextures() is called correctly. However, the GPU memory is not freed as the memory monitor of GPU-Z suggests (as well as the general performance). As soon, as I manually make that call exclusive/synchronized, the memory leak seems to not occur again.

This article is not too specific how OpenGL handles concurrent deletion of textures/buffers. However, we definitely take care of correct thread-context management. It might be a nVidia driver bug as well... :/

Assignee
Assign to
Time tracking

LRZ Homepage | Datenschutz | Dokumentation und Betriebsbedingungen | Impressum