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

currentNcFiles memory usage #94

Closed
simonbyrne opened this issue Jul 1, 2019 · 4 comments
Closed

currentNcFiles memory usage #94

simonbyrne opened this issue Jul 1, 2019 · 4 comments

Comments

@simonbyrne
Copy link

I just tracked down a large memory leak to the existence of currentNcFiles: while the fix is easy (calling ncclose 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?

@visr
Copy link
Member

visr commented Jul 2, 2019

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.

@meggart
Copy link
Member

meggart commented Jul 2, 2019

I agree this should have high priority to be fixed, and maybe just picking the parts that remove the currentNcFiles stuff from #61 as a smaller PR might be not too much work. I am not so full this week and will give it a try.

@natgeo-wong
Copy link

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?

@visr
Copy link
Member

visr commented Oct 24, 2019

Hmm this is already fixed in #95, but I see we haven't tagged a release yet. Should do so shortly.

@visr visr closed this as completed Oct 24, 2019
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

4 participants