Memory leak in pvbatch using --use-offscreen-rendering
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
I have a user that is having problems with memory leaks in pvbatch, using --use-offscreen-rendering. Here is his excellent writeup:
Summary: ParaView pvbatch: memory leak using --use-offscreen-rendering Notes: Create Date: 7/27/2011 6:24:05 PM I'm running into an error where the memory footprint of pvbatch keeps growing, despite the data set size remaining the same. This only occurs when using the "--use-offscreen-rendering" option in pvbatch. Unfortunately, I need that option to execute things on redsky, as the job hangs without it.
This bug is present in 3.10.0 and 3.10.1 (Linux 64-bit), but is not present in 3.8.0 or 3.8.1 (Linux 64-bit). I've run this locally and on redsky and got the same results.
My dataset is rather large, but I've reproduced the problem with the following simple script:
--- memory.py --- from paraview.simple import * view = CreateRenderView() view.ViewSize = [700, 400] source = Sphere(PhiResolution = 1024, ThetaResolution = 1024) display = Show(source) Render()
loops=20 for i in range(loops): print "on iteration %d/%d" % (i, loops) source.PhiResolution = 512 source.ThetaResolution = 512 Render() source.PhiResolution = 1024 source.ThetaResolution = 1024 Render()
To replicate:
- run "mpiexec -n 4 pvbatch --use-offscreen-rendering memory.py"
- notice the memory footprint climbs to about 5 GB at the end of the script
To see desired behavior:
- run "mpiexec -n 4 pvbatch memory.py"
- notice memory footprint never grows larger than about 1 GB
If you change the number of loops to 100 or so, it'll eventually crash due to memory.
Thanks, Tim