I am adding and deleting sphere source with resolution 80000, and open memory inspector to monitor the memory change, i found the memory is increasing all the time…
What i expect is the memory should not increase after i delete the source
How to fix this issues?
Thanks and Best Regards,
Using this script (2.0 KB) as a macro, I was able to reproduce the behavior for the first 10 spheres, 10Mb of memory by sphere, but it then stops increasing.
Do you see the same behavior ?
This should not happen ideally, but not critical imo.
I wonder if this has to do with ParaView’s memory handling code. I believe i was told that ParaView doesn’t “return” memory that it uses to the system, but it does know when it’s free, and adds it to the free memory pool to be used. An example where this works correctly, but is really confisuing, is remote server if you open something large, delete it, and open something large a second time. The big no-no is memory should never grow until we crash. And, from Mathieu;s experiments, sounds like it doesn’t.
Thank you Mathieu for your reply!
i am not good at python script, i did it manually, i did not make it reach 10M, just tried several times.
What confused me is why paraview failed to release memory after i delete the object in pipeline browser…?
In my situation, very big memory is needed, so such memory increase is unacceptable… any suggestions or ideas ?
Thanks a lot!
Your example usecase uses maximum 600Mo, hardly too much memory.
What are the numbers of your real usecase ?
How to manage memory in paraview elegantly?
Why after I delete object in pipeline browser, the memory is not released?