-
Notifications
You must be signed in to change notification settings - Fork 17
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
Possible memory leak in mincWriteVolume #302
Comments
Is |
The minc-toolkit default environment sets it as:
|
Hmm, quite possible it is a memory leak in the C bindings or similar. Is this memory measurement the whole machine or your R process? If the latter, do you know if the dip at 3.30pm corresponds to the beginning of writing files? Do I have access to your modules/files on Niagara? If so I could try to debug by running under Valgrind but I'm pretty unfamiliar with RMINC internals so might be challenging. |
This is the Niagara readout from the slurm whole-machine statistics
Yes
For now, we're addressing this by randomizing the list of files to write out and repeating the job so we'll eventually get them all. |
Just as a quick note -- as a better workaround than randomizing, you could probably run mincWriteVolume from short-lived subprocesses e.g. using |
Thanks. Is there any chance you could give me read access (via extended ACLs, say) to the data directory as well? |
I have a special share for that,
You have read-write there. Data is still copying. I suggest ~30 minutes wait. |
Are the jacobians being copied as well ? |
Yes. Warning: the file paths are all absolute path. Student will be talked to. |
We're running the following code on Niagara:
And seeing the following memory performance:
During this time, we loop through and get ~29 files saved, before the system runs out of memory and kills R.
we're not creating any new memory-holding objects as far as I understand, but R memory consumption rises and eventually fills the node.
The text was updated successfully, but these errors were encountered: