Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zarr backing MDA display can overflow disk space - maybe make location configurable #240

Open
ianhi opened this issue Jan 11, 2023 · 0 comments

Comments

@ianhi
Copy link
Contributor

ianhi commented Jan 11, 2023

In #145 (review) @tlambert03 noted

In the future, it'd be nice to bring back the in-memory behavior as well if someone knows they won't be exceeding their RAM (along with checks to let you know whether you would be).

In that same vein it turns out you can also muck things up by running out of hard drive space :(
image

We have a multi-terabyte data drive on that computer which is where I save images, but the zarr location isn't configurable to use that directory. Interestingly since the saving mechanism is separate and uses the other drive it appears to continue functioning.

I think there are two opportunities for improvement here:

  1. Prevention: Allow some configurability in where the temp files are made
  2. Damage control: Catch and raise a Napari dialog with the error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant