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 on repeat call to leapfrog #2

Open
krober10nd opened this issue Jan 15, 2021 · 3 comments
Open

memory leak on repeat call to leapfrog #2

krober10nd opened this issue Jan 15, 2021 · 3 comments

Comments

@krober10nd
Copy link
Collaborator

  • Memory grows on each successive call to leapfrog which is problematic obviously for FWI.
  • Investigating...will post an image shortly.
@krober10nd
Copy link
Collaborator Author

  • generational garbage collector is not experiencing sufficient pressure to be called.
  • Here I call the garbage collector manually at the end of the forward problem to release the memory occupied by symbolics.
    testing_wo_gc
    testing_w_gc
  • Solution: gc.collect() at the end of each FWI iteration

@krober10nd
Copy link
Collaborator Author

this is being addressed by rewriting solvers in a class-based structure #3

@krober10nd
Copy link
Collaborator Author

firedrakeproject/firedrake#1617

If we call gc then we have to disable it to avoid hang ups

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

No branches or pull requests
1 participant
@krober10nd