Skip to content

Conversation

@laldoroty
Copy link
Collaborator

No description provided.

@laldoroty laldoroty requested a review from rknop July 7, 2025 03:50
@laldoroty laldoroty linked an issue Jul 7, 2025 that may be closed by this pull request
@laldoroty laldoroty requested a review from wmwv July 7, 2025 03:57
Copy link
Collaborator

@wmwv wmwv left a comment

Choose a reason for hiding this comment

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

LGTM

Editorializing: I think this memory tracing and freeing would be largely unnecessary if the subtraction processing was separated out into a function that loaded an image and ran just one subtraction. That would make it easy for Python to figure out it didn't need the memory anymore after the function returned. Having this for loop that runs all of this stuff and then explicitly calling self.image.free() is kind of trying to recreate what you would get naturally if this big block were just its own function.

@laldoroty laldoroty merged commit 4d537c2 into main Jul 8, 2025
3 checks passed
github-actions bot pushed a commit that referenced this pull request Jul 8, 2025
free memory. update phrosty_config.yaml to match 4d537c2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Trace memory

3 participants