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 740
    • Issues 740
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 198
    • Merge requests 198
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTK
  • VTKVTK
  • Issues
  • #1558
Closed
Open
Created Jan 31, 2005 by Kitware Robot@kwrobotOwner

potential memory leak in vtkImageReslice

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.


The destructor of vtkImageReslice should decrease the reference count of its InformationInput.

$ vtk % vtkImageReslice reslice reslice % vtkImageData data data % data GetReferenceCount 1 % reslice SetInformationInput data % data GetReferenceCount 2 % reslice Delete % data GetReferenceCount 2

The last result should be 1. A fix is:

//---------------------------------------------------------------------------- vtkImageReslice::~vtkImageReslice() {

  • this->SetInformationInput(NULL); this->SetResliceTransform(NULL); this->SetResliceAxes(NULL); if (this->IndexMatrix)
Assignee
Assign to
Time tracking