Skip to content

TS-4746: ParentRecord *secondary_parents malloc, but no place free,which will cause memery leak#902

Closed
keith2008 wants to merge 4 commits intoapache:masterfrom
keith2008:TS-4746
Closed

TS-4746: ParentRecord *secondary_parents malloc, but no place free,which will cause memery leak#902
keith2008 wants to merge 4 commits intoapache:masterfrom
keith2008:TS-4746

Conversation

@keith2008
Copy link
Copy Markdown
Contributor

ParentRecord *secondary_parents malloc, but no place free,which will cause memery leak

@PSUdaemon PSUdaemon added this to the 7.0.0 milestone Aug 23, 2016
@zwoop
Copy link
Copy Markdown
Contributor

zwoop commented Aug 23, 2016

Just to be picky, but we should avoid typos in the commit messages (memory, not memory). I also think this could be simplified to just e.g.

4746 Fixes ParentRecord *secondary_parents memory leak

@zwoop
Copy link
Copy Markdown
Contributor

zwoop commented Aug 23, 2016

Also, I'm pretty sure this would fail the CI build, please run "make clang-format" on the code, and push this again with the updated commit message.

Thanks!

@zwoop zwoop self-assigned this Aug 23, 2016
@jrushford
Copy link
Copy Markdown
Contributor

I don't think the NULL check on the pointer is required as ats_free does that under the hood.

@jrushford jrushford closed this Aug 25, 2016
@jrushford
Copy link
Copy Markdown
Contributor

Closing this PR on behalf of keith2008 due to merge conflicts. I am creating a new PR for this.

@keith2008 keith2008 deleted the TS-4746 branch August 31, 2016 02:29
@zwoop zwoop modified the milestone: 7.0.0 May 4, 2017
bneradt pushed a commit to bneradt/trafficserver that referenced this pull request Feb 9, 2024
argc,argv wasn't properly set to let the remap getopt handle them
correctly. This fix set the right value and pointer for the getopt
to work with.

(cherry picked from commit b0bf17d)

Co-authored-by: Damian Meden <dmeden@apache.org>
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.

4 participants