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.

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

multi: avoid memory-leak risk #13471

Closed
wants to merge 1 commit into from
Closed

multi: avoid memory-leak risk #13471

wants to merge 1 commit into from

Conversation

bagder
Copy link
Member

@bagder bagder commented Apr 25, 2024

'newurl' is allocated in some conditions and used in a few scenarios, but there were theoretical combinations in which it would not get freed. Move the free to happen unconditionally. Never triggered by tests, but spotted by Coverity.

'newurl' is allocated in some conditions and used in a few scenarios,
but there were theoritecal combinations in which it would not get freed.
Move the free to happen unconditionally. Never trigged by tests, but
spotted by Coverity.
@bagder bagder closed this in 3572dd6 Apr 25, 2024
@bagder bagder deleted the bagder/multi-leak branch May 6, 2024 21:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

1 participant