Henry Robinson commented on ZOOKEEPER-768:

Note that this is the same assertion as in ZOOKEEPER-707, which is not related 
to the python client. 

I need to understand why it's an error for the completion callback to be null 
when processing a ping, since send_ping explicitly queues a null callback... 

> zkpython segfault on close (assertion error in io thread)
> ---------------------------------------------------------
>                 Key: ZOOKEEPER-768
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-768
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: contrib-bindings
>    Affects Versions: 3.4.0
>         Environment: ubuntu lucid (10.04), zookeeper trunk (java/c/zkpython)
>            Reporter: Kapil Thangavelu
>         Attachments: zkpython-segfault-client-log.txt, 
> zkpython-segfault-on-close-core.bz2, zkpython-segfault-stack-traces.txt, 
> zkpython-segfault.py
> While trying to create a test case showing slow average add_auth, i stumbled 
> upon a test case that reliably segfaults for me, albeit with variable amount 
> of iterations (anwhere from 0 to 20 typically). fwiw, I've got about 220 
> processes in my test environment (ubuntu lucid 10.04). The test case opens a 
> connection, adds authentication to it, and closes the connection, in a loop. 
> I'm including the sample program and the gdb stack traces from the core file. 
> I can upload the core file if thats helpful.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to