Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
ParaView
ParaView
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 2,007
    • Issues 2,007
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 57
    • Merge Requests 57
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ParaView
  • ParaViewParaView
  • Issues
  • #16975

Closed
Open
Opened Oct 20, 2016 by Utkarsh Ayachit@utkarsh.ayachit
  • Report abuse
  • New issue
Report abuse New issue

"Multicorrelative Statistics" causes leaks

  • start ParaVIew, builtin
  • Open can.ex2, Apply
  • Create "Multicorrelative Statistics" filer, Apply Quit ParaView. If you built ParaView with VTK_DEBUG_LEAKS CMake variable set to ON, then you'll get this:
vtkDebugLeaks has detected LEAKS!
Class "vtkInformationVector" has 4 instances still around.
Class "vtkIntArray" has 2 instances still around.
Class "vtkInformation" has 120 instances still around.
Class "vtkStringArray" has 2 instances still around.
Class "vtkInformationDoubleVectorValue" has 118 instances still around.
Class "9vtkBufferIcE" has 2 instances still around.
Class "9vtkBufferIiE" has 2 instances still around.
Class "vtkCharArray" has 2 instances still around.
  • Here's the valgrind log.
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: paraview/paraview#16975