-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Fixed unnecessary transfer of the ownership before release which returns the pointer itself #11726
Merged
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change | ||||||
---|---|---|---|---|---|---|---|---|
|
@@ -382,10 +382,10 @@ void writeTextIdentificationFrame( | |||||||
auto pFrame = | ||||||||
std::make_unique<TagLib::ID3v2::TextIdentificationFrame>(id, stringType); | ||||||||
pFrame->setText(toTString(text)); | ||||||||
pTag->addFrame(pFrame.get()); | ||||||||
// Now that the plain pointer in pFrame is owned and managed by | ||||||||
// pTag we need to release the ownership to avoid double deletion! | ||||||||
pFrame.release(); | ||||||||
|
||||||||
// Release returns a pointer to the managed object and releases the ownership, | ||||||||
// the plain pointer in pFrame is owned and managed by pTag | ||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Something like this should be sufficient
Suggested change
|
||||||||
pTag->addFrame(pFrame.release()); | ||||||||
} | ||||||||
} | ||||||||
|
||||||||
|
@@ -414,10 +414,10 @@ void writeUserTextIdentificationFrame( | |||||||
std::make_unique<TagLib::ID3v2::UserTextIdentificationFrame>(stringType); | ||||||||
pFrame->setDescription(toTString(description)); | ||||||||
pFrame->setText(toTString(text)); | ||||||||
pTag->addFrame(pFrame.get()); | ||||||||
// Now that the plain pointer in pFrame is owned and managed by | ||||||||
// pTag we need to release the ownership to avoid double deletion! | ||||||||
pFrame.release(); | ||||||||
|
||||||||
// Release returns a pointer to the managed object and releases the ownership, | ||||||||
// the plain pointer in pFrame is owned and managed by pTag | ||||||||
pTag->addFrame(pFrame.release()); | ||||||||
} | ||||||||
} | ||||||||
} | ||||||||
|
@@ -488,10 +488,10 @@ void writeCommentsFrame( | |||||||
std::make_unique<TagLib::ID3v2::CommentsFrame>(stringType); | ||||||||
pFrame->setDescription(toTString(description)); | ||||||||
pFrame->setText(text); | ||||||||
pTag->addFrame(pFrame.get()); | ||||||||
// Now that the plain pointer in pFrame is owned and managed by | ||||||||
// pTag we need to release the ownership to avoid double deletion! | ||||||||
pFrame.release(); | ||||||||
|
||||||||
// Release returns a pointer to the managed object and releases the ownership, | ||||||||
// the plain pointer in pFrame is owned and managed by pTag | ||||||||
pTag->addFrame(pFrame.release()); | ||||||||
} | ||||||||
} | ||||||||
// Cleanup: Remove non-standard comment frames to avoid redundant and | ||||||||
|
@@ -576,10 +576,10 @@ void writeGeneralEncapsulatedObjectFrame( | |||||||
pFrame->setDescription(toTString(description)); | ||||||||
pFrame->setObject(toTByteVector(data)); | ||||||||
pFrame->setMimeType(mimeType); | ||||||||
pTag->addFrame(pFrame.get()); | ||||||||
// Now that the plain pointer in pFrame is owned and managed by | ||||||||
// pTag we need to release the ownership to avoid double deletion! | ||||||||
pFrame.release(); | ||||||||
|
||||||||
// Release returns a pointer to the managed object and releases the ownership, | ||||||||
// the plain pointer in pFrame is owned and managed by pTag | ||||||||
pTag->addFrame(pFrame.release()); | ||||||||
} | ||||||||
} | ||||||||
|
||||||||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comment is obsolete after dropping the 2-step get-release pattern. Repeating the std definition of release() is pointless and confusing. Also applies to other locations in the code.
The 2-step pattern is required for exception safe C++ programming. But since any exception thrown by addFrame() is expected to be fatal a resource leak doesn't matter then.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This code has been written with purpose and the comment explained why. If you decide to take a simpler approach then delete the obsolete comment. I don't care, does not really matter. But please change it in a consistent way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The resource leak reported by Coverity is obviously a false positive.