[ 
https://issues.apache.org/jira/browse/TS-4872?focusedWorklogId=29171&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-29171
 ]

ASF GitHub Bot logged work on TS-4872:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 15/Sep/16 19:03
            Start Date: 15/Sep/16 19:03
    Worklog Time Spent: 10m 
      Work Description: GitHub user jpeach opened a pull request:

    https://github.com/apache/trafficserver/pull/1025

    TS-4872: Fix clang-analyzer leak error on LogObject.cc _checkout_write.

    We could not quite figure out why it reports this (smells almost like a bug 
in clang-analyzer), but some refactoring that avoids the warning, and cleans up 
the code overall.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jpeach/trafficserver fix/4872

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafficserver/pull/1025.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1025
    
----

----


Issue Time Tracking
-------------------

            Worklog Id:     (was: 29171)
            Time Spent: 10m
    Remaining Estimate: 0h

> clang-analyzer: Memory leak LogObject.cc _checkout_write
> --------------------------------------------------------
>
>                 Key: TS-4872
>                 URL: https://issues.apache.org/jira/browse/TS-4872
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core
>            Reporter: Leif Hedstrom
>            Assignee: James Peach
>              Labels: clang-analyzer
>             Fix For: 7.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> We could not quite figure out why it reports this (smells almost like a bug 
> in clang-analyzer), but [[email protected]] has a refactoring that avoids 
> the warning, and cleans up the code overall.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to