[
https://issues.apache.org/jira/browse/ZOOKEEPER-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678803#action_12678803
]
Patrick Hunt commented on ZOOKEEPER-332:
----------------------------------------
I did do a quick eyeball of the results before entering the jira - I guess the
"goto fail" in getaddrs caught my eye - that skips the freeaddrinfo call, but
now looking again it seems thats an unlikely case (oom).
Feel free to close, it might be good to document this somewhere, perhaps a
src/c/valgrind.txt file that details the exceptions in case someone else runs
valgrind? Isn't there some way to pass known exceptions to valgrind? Perhaps
that's a better way (commit the exceptions to svn).
anyway - looks like we are good for 3.1.1, feel free to close.
> c client issues (memory leaks) reported by valgrind
> ---------------------------------------------------
>
> Key: ZOOKEEPER-332
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-332
> Project: Zookeeper
> Issue Type: Bug
> Components: c client
> Affects Versions: 3.1.0
> Reporter: Patrick Hunt
> Priority: Blocker
> Fix For: 3.1.1, 3.2.0
>
> Attachments: valgrind_mt.out, valgrind_st.out
>
>
> Attaching valgrind log files.
> 1) getpwuid_r doesn't seem like it's due to us
> 2) the rest seem to be valid
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
