Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK VTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 737
    • Issues 737
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 209
    • Merge requests 209
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTK
  • VTKVTK
  • Issues
  • #17967

Closed
Open
Created Jul 24, 2020 by Ivan Manuylovich@ivan.manuylovich

vtkAutoInit mechanism has broken

vtkAutoInit mechanism has broken after some recent Windows update (as I suppose). This was tested both for VTK-8.2 and VTK-9.0 on the simplest program with vtkAutoInit.h header included. VTK_DEBUG_LEAKS had been switched on. Debugging shows that vtkDebugLeaksManager constructor is called many times when VTK dlls are being loaded automatically for other VTK dlls. vtkDebugLeaksManagerCount value grows after each constructor execution. But vtkDebugLeaksManager destructors are not called during program termination. The test program contains nothing except "vtkObjectBase *pObjectBase=vtkObjectBase::New();" to test memory leak.

Assignee
Assign to
Time tracking