You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Susan Hinrichs (JIRA)" <ji...@apache.org> on 2016/05/06 03:57:12 UTC

[jira] [Assigned] (TS-4421) Leak of INKContInternal

     [ https://issues.apache.org/jira/browse/TS-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Susan Hinrichs reassigned TS-4421:
----------------------------------

    Assignee: Susan Hinrichs

> Leak of INKContInternal
> -----------------------
>
>                 Key: TS-4421
>                 URL: https://issues.apache.org/jira/browse/TS-4421
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Susan Hinrichs
>            Assignee: Susan Hinrichs
>
> Reported by [~sunwei] after upgrading to a build with the TS-3612 changes.  Tracked it down to problems with the m_event_count.  In INKContInternal::destroy, we call schedule_imm to try the destory later if the m_deletable flag is not set.  But we do not bump the m_event_count before calling schedule.  The event handler will decrement m_event_count one more time than it was incremented, so by the time we try test the object for being deletable, m_event_count is too low.



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