Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • ParaView ParaView
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,848
    • Issues 1,848
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 93
    • Merge requests 93
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaView
  • ParaViewParaView
  • Issues
  • #10702

Closed
Open
Created May 10, 2010 by Kitware Robot@kwrobotOwner

XDMF/HDF5 reader memory leak

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


I'm experiencing a memory leak with the XDMF reader when trying to create an animation of the data contained in a set of HDF5 files. My approach is as follows:

  1. One XDMF file which is a temporal collection containing links to a list of other XDMF files
  2. One XDMF file for each time step (linked to by the XDMF file above), each of which is a spatial collection of several 2D structured grids. The data for the grids is contained in HDF5 files (also one for each time step).

When I open the file with the temporal collection in Paraview, the data shows up as a temporal collection as expected. I can step back and forth in time and everything seems to work just fine. However, as I load in more time steps (by stepping forward in time), Paraview's memory usage keeps increasing. It seems like it is not freeing the memory associated with the old time step when reading in a new one.

To illustrate this problem, I've uploaded a collection of XDMF and HDF5 files.

There are 10 time steps in the collection. The data set is very small, but it should still show the problem (I could easily generate larger data sets if necessary). I get the same behaviour in Paraview 3.6 and 3.8 on both Centos 5.3 (64 bit) and Mac OS X 10.5.

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