[Paraview] Memory leak with Catalyst

[Gallagher, Timothy P]

Hi,


One of our users is running a very big simulation and writing out images of two slices (two different views) every 1000 iterations and writing out the data for the two slices (two different data writers) as VTK files every 5000 iterations. It is using Paraview 4.4.


After 21000 iterations, the simulation is killed because the memory on the compute nodes fills up. I usually know how to track down memory problems in our code using valgrind and related tools, but is that the right way to go to try and find this problem?


Are there any tips on how to isolate where the problem may be? I don't know if it is in the adapter, or in paraview itself. Has anybody encountered problems with runaway memory using Catalyst in 4.4 when writing images or VTK files?


I know when we use pvpython to generate images and loop over many files, sometimes the memory also blows up and so we usually move the loop over the files outside the pvpython script and into a driver script that executes a new pvpython for each file. Is there a way to shut down/start up Catalyst each time it needs to write something? Is that advisable?


Thanks,


Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160520/ec9bb46e/attachment.html>