When loading OME-Zarr (.zarr) image data into napari using the napari-ome-zarr plugin, I have noticed that deleting layers from the viewer does not free the corresponding data from working memory. The memory usage remains high even after layers are removed. This suggests that references to the image data persist.
Steps to Reproduce
- Load a .zarr file (OME-Zarr format) into napari via napari-ome-zarr.
- Delete/remove layers from the viewer.
- Observe that memory usage does not decrease as expected.
Expected Behavior
Upon removing layers from the napari viewer, the memory associated with those layers, including any cached dask arrays or image data from the .zarr source, should be released promptly to prevent memory bloat during long sessions.
Edit: Napari behavior for TIFs seems to be that after removing layers data stays in memory but when loading a new image, old data is removed from memory.
Observed Behavior
Memory used by the application does not decrease despite deleting layers, indicating that the data stays in memory.
When loading OME-Zarr (.zarr) image data into napari using the napari-ome-zarr plugin, I have noticed that deleting layers from the viewer does not free the corresponding data from working memory. The memory usage remains high even after layers are removed. This suggests that references to the image data persist.
Steps to Reproduce
Expected Behavior
Upon removing layers from the napari viewer, the memory associated with those layers, including any cached dask arrays or image data from the .zarr source, should be released promptly to prevent memory bloat during long sessions.
Edit: Napari behavior for TIFs seems to be that after removing layers data stays in memory but when loading a new image, old data is removed from memory.
Observed Behavior
Memory used by the application does not decrease despite deleting layers, indicating that the data stays in memory.