[
https://issues.apache.org/jira/browse/TS-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245856#comment-15245856
]
ASF GitHub Bot commented on TS-3429:
------------------------------------
GitHub user shinrich opened a pull request:
https://github.com/apache/trafficserver/pull/576
TS-3429: Fix reference counting for TSContScheduleEvery.
Changed the logic at the end of the INKContInternal event handler to bump
up the ref-count at the end if it was invoked for an interval event. This
enables the ref count to be incremented before every call to the event handler.
I ran with the Epic plugin (referenced by related bug), and its stats
handler function executed multiple times without assertion failures.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shinrich/trafficserver ts-3429
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/576.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 #576
----
commit 3c1f2814e3524ca40e355d591f9f97fdd46d3b24
Author: shinrich <[email protected]>
Date: 2016-04-18T15:15:16Z
TS-3429: Fix reference counting for TSContScheduleEvery.
----
> TSContScheduleEvery does not increment event count correctly
> ------------------------------------------------------------
>
> Key: TS-3429
> URL: https://issues.apache.org/jira/browse/TS-3429
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Reporter: Bin
> Assignee: Susan Hinrichs
> Fix For: 6.2.0
>
>
> TSContScheduleEvery only increments the event count the first time it is
> scheduled. When the event handler gets invoked, it decrements the event
> count. So it triggers the assertion at InkAPI.cc:987.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
