# clean ram memory after deleting source filter

**URL:** https://discourse.paraview.org/t/clean-ram-memory-after-deleting-source-filter/17318
**Category:** ParaView Support
**Created:** [November 19, 2025, 10:52am UTC](https://discourse.paraview.org/t/clean-ram-memory-after-deleting-source-filter/17318 "2025-11-19T10:52:28Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![otaolafr](https://discourse.paraview.org/user_avatar/discourse.paraview.org/otaolafr/32/3595_2.png) [@otaolafr](https://discourse.paraview.org/u/otaolafr)
#### Post date: [November 20, 2025, 9:24am UTC](https://discourse.paraview.org/t/clean-ram-memory-after-deleting-source-filter/17318/7 "2025-11-20T09:24:32Z")

</div>

In the two cases, if I open the raw data using the GUI with the image reader or if i do it in python using the function mentionned here [crashing when using clip over Image (Uniform Rectilinear Grid)](https://discourse.paraview.org/t/crashing-when-using-clip-over-image-uniform-rectilinear-grid/17320)

in the case of the GUI, i select the filter and simply delete it

in the case of python, i tested the two options, select the filter and simply delete it, and use Delete(filter)  
in non of the cases the ram is being free, and therefore when I run the python function again OR import using the GUI on exactly same file (so memory should be enough, and when importing first time i had around 5 gb extra free) paraview simply crashes for lack of memory.

---

_[View the full topic](https://discourse.paraview.org/t/clean-ram-memory-after-deleting-source-filter/17318)._