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.

Sign up for GitHub

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

Jump to bottom

Memory leak when restarting reconstruction? #187

Closed
carterbox opened this issue Feb 8, 2022 · 0 comments · Fixed by #192
Closed

Memory leak when restarting reconstruction? #187

carterbox opened this issue Feb 8, 2022 · 0 comments · Fixed by #192

Comments

@carterbox
Copy link
Contributor

I seems that restarting a reconstruction has a memory overhead that increases with each restart. This causes out of memory error. For example, restarting the reconstruction 10 times with 10 iterations each time consumes more memory than doing one reconstruction with 100 iterations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix memory leak due to CuPy automatic FFT Cache carterbox/tike
1 participant
@carterbox