ICU-21537 Fix invalid free by long locale name #1656
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.
Only free baseName when it is neither the same as fullName nor fullNameBuffer.
If we have a very long base name (say a lot of variant) and one extension, the set extension will return buffer error and
the cause Locale to reallocate buffer for fullName, but baseName is still pointing to fullNameBase.
Then later if we free baseName in the destructor we will free the memory part of the locale itself (because
it is still pointing to fullNameBuffer) . So we need to check the free of baseName not only if it is different from fullName, but also differ from fullNameBuffer.
To test
Checklist