Skip to content

ext/intl usmg_parse_helper possible mem leak fixes on failure path. #10830

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.

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

Closed
wants to merge 1 commit into from

Conversation

devnexen
Copy link
Member

introducing an utility class which calls a lambda from its destructor when going out of scope.

Copy link
Member

@Girgias Girgias left a comment

Choose a reason for hiding this comment

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

I suppose the cleanup_zvals() macro didn't handle this? In which case the Formattable::kString could be used to detect the memory leak potentially?

introducing an utility class which calls a lambda from its destructor
when going out of scope.
@Girgias
Copy link
Member

Girgias commented Aug 7, 2025

Btw @devnexen is this still relevant?

@devnexen
Copy link
Member Author

devnexen commented Aug 8, 2025

The ideas themselves yes, maybe not in this form.

@devnexen devnexen closed this Aug 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants