[
https://issues.apache.org/jira/browse/ZOOKEEPER-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-888:
-----------------------------------
Fix Version/s: 3.4.0
3.3.2
Borderline blocker, Henry any insight on this? Something that can be addressed
for 3.3.2?
> c-client / zkpython: Double free corruption on node watcher
> -----------------------------------------------------------
>
> Key: ZOOKEEPER-888
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-888
> Project: Zookeeper
> Issue Type: Bug
> Components: c client, contrib-bindings
> Affects Versions: 3.3.1
> Reporter: Lukas
> Priority: Critical
> Fix For: 3.3.2, 3.4.0
>
> Attachments: resume-segfault.py
>
>
> the c-client / zkpython wrapper invokes already freed watcher callback
> steps to reproduce:
> 0. start a zookeper server on your machine
> 1. run the attached python script
> 2. suspend the zookeeper server process (e.g. using `pkill -STOP -f
> org.apache.zookeeper.server.quorum.QuorumPeerMain` )
> 3. wait until the connection and the node observer fired with a session
> event
> 4. resume the zookeeper server process (e.g. using `pkill -CONT -f
> org.apache.zookeeper.server.quorum.QuorumPeerMain` )
> -> the client tries to dispatch the node observer function again, but it was
> already freed -> double free corruption
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
