You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Chris Darroch (JIRA)" <ji...@apache.org> on 2009/03/03 20:44:56 UTC

[jira] Commented: (ZOOKEEPER-332) c client issues (memory leaks) reported by valgrind

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678428#action_12678428 ] 

Chris Darroch commented on ZOOKEEPER-332:
-----------------------------------------

These look OK to me, on a first glance.  There's a call to freeaddrinfo() in getaddrs() to match getaddrinfo().  There's also a free(zh) in zookeeper_close() to match the allocation in zookeeper_init().  I think these are just spurious reports from valgrind, but I'm not absolutely 100% on that.

> 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.