Skip to content

Conversation

@ZigzagAK
Copy link

@ZigzagAK ZigzagAK commented Dec 3, 2025

Please, review this patch.

Copy link
Contributor

@jrgemignani jrgemignani left a comment

Choose a reason for hiding this comment

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

See comments. Looks good otherwise.

@ZigzagAK ZigzagAK force-pushed the bugfix/possible-memory-leaks branch from 20683d4 to f174545 Compare December 4, 2025 08:36
@ZigzagAK ZigzagAK requested a review from jrgemignani December 4, 2025 08:37
Copy link
Contributor

@jrgemignani jrgemignani left a comment

Choose a reason for hiding this comment

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

@ZigzagAK There was an update to the master branch that also had changes to age load. Could you rebase this PR off of the latest master, please :) Otherwise, everything looks good.

@ZigzagAK
Copy link
Author

ZigzagAK commented Dec 5, 2025

@ZigzagAK There was an update to the master branch that also had changes to age load. Could you rebase this PR off of the latest master, please :) Otherwise, everything looks good.

Already rebased.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants