You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Yuliya Feldman (JIRA)" <ji...@apache.org> on 2016/11/04 01:31:58 UTC
[jira] [Commented] (ZOOKEEPER-2509) Secure mode leaks memory
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634884#comment-15634884 ]
Yuliya Feldman commented on ZOOKEEPER-2509:
-------------------------------------------
Ping again. It has been 6 weeks already
[~phunt], [~rgs] - Could you please review the patch, as it seems you are the most familiar with the code in question.
> Secure mode leaks memory
> ------------------------
>
> Key: ZOOKEEPER-2509
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2509
> Project: ZooKeeper
> Issue Type: Bug
> Affects Versions: 3.5.1, 3.5.2
> Reporter: Ted Dunning
> Assignee: Ted Dunning
> Fix For: 3.5.3, 3.6.0
>
> Attachments: 0001-Updated-patch-for-Netty-leak-testing-to-trunk.patch, ZOOKEEPER-2509-1.patch, ZOOKEEPER-2509.patch, ZOOKEEPER-2509.patch, ZOOKPEEPER-2509.patch, leak-patch.patch
>
>
> The Netty connection handling logic fails to clean up watches on connection close. This causes memory to leak.
> I will have a repro script available soon and a fix. I am not sure how to build a unit test since we would need to build an entire server and generate keys and such. Advice on that appreciated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)