[ 
https://issues.apache.org/jira/browse/TS-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135095#comment-15135095
 ] 

ASF GitHub Bot commented on TS-4178:
------------------------------------

GitHub user bryancall opened a pull request:

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

    TS-4178: Memory leak in SplitDNSConfig

    

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

    $ git pull https://github.com/bryancall/trafficserver ts-4178

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

    https://github.com/apache/trafficserver/pull/457.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 #457
    
----
commit da6f54d8d63d8b29266d31d2f031b2ee627a44e8
Author: Bryan Call <[email protected]>
Date:   2016-02-05T21:55:40Z

    TS-4178: Memory leak in SplitDNSConfig

----


> Memory leak in SplitDNSConfig
> -----------------------------
>
>                 Key: TS-4178
>                 URL: https://issues.apache.org/jira/browse/TS-4178
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: DNS
>    Affects Versions: 6.1.0
>            Reporter: Bryan Call
>            Assignee: Bryan Call
>             Fix For: 6.2.0
>
>
> {code}
> =================================================================
> ==7628==ERROR: LeakSanitizer: detected memory leaks
> Direct leak of 8 byte(s) in 1 object(s) allocated from:
>     #0 0x7f27d1b01872 in operator new(unsigned long) 
> (/lib64/libasan.so.2+0x99872)
>     #1 0xa1a1c3 in SplitDNSConfig::startup() 
> /home/bcall/dev/apache/trafficserver/iocore/dns/SplitDNS.cc:133
>     #2 0x494e59 in main 
> /home/bcall/dev/apache/trafficserver/proxy/Main.cc:1767
>     #3 0x7f27cea3e57f in __libc_start_main (/lib64/libc.so.6+0x2057f)
> SUMMARY: AddressSanitizer: 8 byte(s) leaked in 1 allocation(s).
> {code}



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

Reply via email to