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

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

                Author: ASF GitHub Bot
            Created on: 19/Jul/16 00:11
            Start Date: 19/Jul/16 00:11
    Worklog Time Spent: 10m 
      Work Description: GitHub user jacksontj opened a pull request:

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

    TS-4684 Leaked references to HostDBInfos from HttpTransact

    

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

    $ git pull https://github.com/jacksontj/trafficserver TS-4684

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

    https://github.com/apache/trafficserver/pull/811.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 #811
    
----
commit ab3b5007ac231cb3ddb3f452eea8a00ed42d04cc
Author: Thomas Jackson <[email protected]>
Date:   2016-07-19T00:11:01Z

    TS-4684 Leaked references to HostDBInfos from HttpTransact

----


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

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

> Leaked references to HostDBInfos from HttpTransact
> --------------------------------------------------
>
>                 Key: TS-4684
>                 URL: https://issues.apache.org/jira/browse/TS-4684
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: HostDB
>            Reporter: Thomas Jackson
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> After running for a while I've noticed a slow leak in memory. After tracking 
> it down the leak is due to not properly decrementing the refcounts in 
> HttpTransact for Ptr<HostDBInfo>. Seems that somewhere in the rebasing this 
> very important line was lost



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

Reply via email to