You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Wenwu Peng (JIRA)" <ji...@apache.org> on 2014/06/16 09:45:02 UTC

[jira] [Updated] (HADOOP-10705) Fix namenode-rpc-unit warning reported by memory leak check tool(valgrind)

     [ https://issues.apache.org/jira/browse/HADOOP-10705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wenwu Peng updated HADOOP-10705:
--------------------------------

    Issue Type: Sub-task  (was: Bug)
        Parent: HADOOP-10388

> Fix namenode-rpc-unit  warning reported by memory leak check tool(valgrind)
> ---------------------------------------------------------------------------
>
>                 Key: HADOOP-10705
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10705
>             Project: Hadoop Common
>          Issue Type: Sub-task
>    Affects Versions: HADOOP-10388
>            Reporter: Wenwu Peng
>
> Rum valgrind to check memory leak for namenode-rpc.unit.
> There are many warning, need to fix it.
> valgrind --tool=memcheck --leak-check=full --show-reachable=yes ./namenode-rpc-unit 
> ==10462== Memcheck, a memory error detector
> ==10462== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
> ==10462== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
> ==10462== Command: ./namenode-rpc-unit
> ==10462== 
> ==10462== HEAP SUMMARY:
> ==10462==     in use at exit: 428 bytes in 12 blocks
> ==10462==   total heap usage: 91 allocs, 79 frees, 16,056 bytes allocated
> ==10462== 
> ==10462== 16 bytes in 1 blocks are indirectly lost in loss record 1 of 12
> ==10462==    at 0x4C2B6CD: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
> ==10462==    by 0x557EB99: __nss_lookup_function (nsswitch.c:456)
> ==10462==    by 0x604863E: ???
> ==10462==    by 0x553744C: getpwuid_r@@GLIBC_2.2.5 (getXXbyYY_r.c:256)
> ==10462==    by 0x42681E: geteuid_string (user.c:67)
> ==10462==    by 0x425ABD: main (namenode-rpc-unit.c:71)



--
This message was sent by Atlassian JIRA
(v6.2#6252)