Fix mem leak regression with Windows' sids API #6984
Merged
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.
Closes #6979 fixing a small regression introduced in #6782 that undid part of #6714
It's easy to forget to free memory with "Caller must free this parameter" APIs like
ConvertStringSidToSidA
, fixed before in #6714 (we even forgot to do it in the wrapper we created forConvertSidToSidStringA
, see #6548 that fixed that).Because a wrapper for
ConvertSidToSidStringA
, I found one place that I changed to use that, instead of the raw API, saving a few lines of code. But in the future, to avoid similar problems withConvertStringSidToSidA
, we'd have to make our own wrapper class forsid
that implemented RAII as noted by @Breakwell.