[
https://issues.apache.org/jira/browse/ZOOKEEPER-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401295#comment-13401295
]
Hudson commented on ZOOKEEPER-1163:
-----------------------------------
Integrated in ZooKeeper-trunk #1597 (See
[https://builds.apache.org/job/ZooKeeper-trunk/1597/])
ZOOKEEPER-1163. Memory leak in zk_hashtable.c:do_insert_watcher_object()
(Anupam Chanda via michim) (Revision 1353683)
Result = SUCCESS
michim : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1353683
Files :
* /zookeeper/trunk/CHANGES.txt
* /zookeeper/trunk/src/c/src/zk_hashtable.c
> Memory leak in zk_hashtable.c:do_insert_watcher_object()
> --------------------------------------------------------
>
> Key: ZOOKEEPER-1163
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1163
> Project: ZooKeeper
> Issue Type: Bug
> Components: c client
> Affects Versions: 3.3.3
> Reporter: Anupam Chanda
> Fix For: 3.3.6, 3.4.4, 3.5.0
>
> Attachments: zookeeper-1163.patch
>
>
> zk_hashtable.c:do_insert_watcher_object() line number 193 calls add_to_list
> with clone flag set to 1. This leaks memory, since the original watcher
> object was already allocated on the heap by activateWatcher() line 330.
> I will upload a patch shortly. The fix is to set clone flag to 0 in the call
> to add_to_list().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
