Free up esmpy object memory#593
Merged
trexfeathers merged 3 commits intoNov 18, 2025
Merged
Conversation
trexfeathers
approved these changes
Nov 18, 2025
1 task
![scitools-ci[bot]](https://avatars.githubusercontent.com/in/212324?s=60&v=4){kind=small}
trexfeathers
approved these changes
Nov 18, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
During initialiasation of regridder objects, esmpy objects used to generate those objects are freed from memory using the
destroy()method. This was being done for theRegridobject, this PR applies this also to theField,GridandMeshesmpy objects used to create theRegridobject. This is especially important when creating many regridders (e.g. as part of #527) and is also especially important when dealing withMeshobjects, which take up more memory.