-
Notifications
You must be signed in to change notification settings - Fork 28
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
currentNcFiles memory usage #94
Comments
Yes getting rid of those global references is an important part of #61. It is a pretty major overhaul, and has gone stale and needs rebasing. If anybody feels like picking that up, that would be great. |
I agree this should have high priority to be fixed, and maybe just picking the parts that remove the |
Hello! I've run into a similar error (although I didn't know it was this at first I went one big round into logging functions), because I handle the downloading and extraction of data from many NetCDF files in my Julia code. I'm currently converting my MATLAB and Python scripts to Julia, and it's a bit jarring that both MATLAB and Python seem to have inbuilt "ncclose()" functionalities within ncread, if you will, whereas this is not the case for Julia. Is this issue still being looked into at the moment? |
Hmm this is already fixed in #95, but I see we haven't tagged a release yet. Should do so shortly. |
I just tracked down a large memory leak to the existence of
currentNcFiles
: while the fix is easy (callingncclose
after reading from each file), the overall approach of keeping a global reference to each opened file is a bit strange. Any reason why this is done?The text was updated successfully, but these errors were encountered: