Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zookeeper.apache.org
Date: Wed, 3 Aug 2016 05:01:20 +0000 (UTC)
From: "Michael Han (JIRA)" <jira@apache.org>
To: dev@zookeeper.apache.org
Message-ID: <JIRA.12994481.1470200474000.207543.1470200480421@Atlassian.JIRA>
In-Reply-To: <JIRA.12994481.1470200474000@Atlassian.JIRA>
References: <JIRA.12994481.1470200474000@Atlassian.JIRA> <JIRA.12994481.1470200474790@arcas>
Subject: [jira] [Created] (ZOOKEEPER-2498) Potential resource leak in C
 client when processing unexpected / out of order response
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 03 Aug 2016 05:01:22 -0000

Michael Han created ZOOKEEPER-2498:
--------------------------------------

             Summary: Potential resource leak in C client when processing unexpected / out of order response
                 Key: ZOOKEEPER-2498
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2498
             Project: ZooKeeper
          Issue Type: Bug
          Components: c client
    Affects Versions: 3.5.2, 3.4.8
            Reporter: Michael Han
            Assignee: Michael Han
             Fix For: 3.4.9, 3.5.3


In C client, we use reference counting to decide if a given zh handle can be destroyed or not. This requires we always make sure to call api_prolog (which increment the counter) and api_epilog (which decrease the counter) in pairs, for a given call context. 

In zookeeper_process, there is a place where the code will return without invoking api_epilog, which would lead to potential zh resource leak.


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