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

Workaround for h5py memory leak #227

Closed
wants to merge 3 commits into from

Conversation

soumickmj
Copy link

No description provided.

@facebook-github-bot
Copy link

Hi @soumickmj!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

@facebook-github-bot facebook-github-bot added the CLA Signed Do not delete this pull request or issue due to inactivity. label Mar 9, 2022
@facebook-github-bot
Copy link

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

Copy link
Contributor

@mmuckley mmuckley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @soumickmj, the copy() commands threw an error for me because h5py datasets don't have the copy() command. You need to convert to a numpy array first.

I tried modifying the PR to convert to a numpy array prior to copy() commands and it didn't for me with the memory issue - I still observed exploding memory. This also included a case where I applied a deepcopy() to the dict.

@@ -345,11 +345,11 @@ def __getitem__(self, i: int):
fname, dataslice, metadata = self.examples[i]

with h5py.File(fname, "r") as hf:
kspace = hf["kspace"][dataslice]
kspace = hf["kspace"][dataslice].copy()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Throws an error.


mask = np.asarray(hf["mask"]) if "mask" in hf else None
mask = np.asarray(hf["mask"].copy()) if "mask" in hf else None
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Throws an error.


target = hf[self.recons_key][dataslice] if self.recons_key in hf else None
target = hf[self.recons_key][dataslice].copy() if self.recons_key in hf else None
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Throws an error.

@soumickmj
Copy link
Author

soumickmj commented Mar 10, 2022

Hi @mmuckley
That's strange. h5py dataset does not have a copy method, but when "hf["kspace"][dataslice]" is called it becomes numpy.ndarray which is then having a copy method.
It is working fine for me with this code:
image

Converting to numpy explicitly and then copy: I tried earlier and that did not resolve the issue for me as well.
But directly calling copy is working for me.

I wonder what's the difference then.
What's the versinon of Python and h5py are you using?

@mmuckley
Copy link
Contributor

This is the full error:

  File "/private/home/mmuckley/projects/fastmri/code/fastMRI/fastmri/data/mri_data.py", line 350, in __getitem__
    mask = np.asarray(hf["mask"].copy()) if "mask" in hf else None
AttributeError: 'Dataset' object has no attribute 'copy'

So the issue might be that you're calling it on the test set and returning None.

We actually have a unit test for __getitem__ here. Could you make sure that your code is passing all lints and unit tests before I test again? You should be able to get unit tests on your fork by renaming your branch to main.

@mmuckley
Copy link
Contributor

Closing due to inactivity.

@mmuckley mmuckley closed this May 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed Do not delete this pull request or issue due to inactivity.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants