Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <346433450.451541266889648095.JavaMail.jira@brutus.apache.org>
Date: Tue, 23 Feb 2010 01:47:28 +0000 (UTC)
From: "Christian Kunz (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-464) Memory leaks in libhdfs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837036#action_12837036 ] 

Christian Kunz commented on HDFS-464:
-------------------------------------

+1 for hdfs-464.rel20.patch except the following section should be deleted (this is when USE_UUGI is not defined, which does not happen)

{code}
@@ -276,12 +281,14 @@ hdfsFS hdfsConnectAsUser(const char* host, tPort port, const char *user , const
           destroyLocalReference(env, jGroups);
         }
         destroyLocalReference(env, jUgi);
+        destroyLocalReference(env, jAttrString);
         return NULL;
       }
       
       destroyLocalReference(env, jUserString);
       destroyLocalReference(env, jGroups);
       destroyLocalReference(env, jUgi);
+      destroyLocalReference(env, jAttrString);
     }
 #endif      
     //Check what type of FileSystem the caller wants...
{code}

> Memory leaks in libhdfs
> -----------------------
>
>                 Key: HDFS-464
>                 URL: https://issues.apache.org/jira/browse/HDFS-464
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: contrib/libhdfs
>    Affects Versions: 0.20.1
>            Reporter: Christian Kunz
>            Assignee: Christian Kunz
>            Priority: Blocker
>             Fix For: 0.21.0, 0.22.0
>
>         Attachments: HADOOP-6034.patch, HDFS-464.patch, hdfs-464.rel20.patch, patch.HADOOP-6034, patch.HADOOP-6034.0.18
>
>
> hdfsExists does not call destroyLocalReference for jPath anytime,
> hdfsDelete does not call it when it fails, and
> hdfsRename does not call it for jOldPath and jNewPath when it fails

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