Return-Path: Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: (qmail 38533 invoked from network); 19 Jan 2010 09:29:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 Jan 2010 09:29:18 -0000 Received: (qmail 4157 invoked by uid 500); 19 Jan 2010 09:29:18 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 4133 invoked by uid 500); 19 Jan 2010 09:29:18 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 4123 invoked by uid 99); 19 Jan 2010 09:29:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jan 2010 09:29:17 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jan 2010 09:29:15 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id E16AB234C4B3 for ; Tue, 19 Jan 2010 01:28:54 -0800 (PST) Message-ID: <1134643153.332371263893334921.JavaMail.jira@brutus.apache.org> Date: Tue, 19 Jan 2010 09:28:54 +0000 (UTC) From: "Eli Collins (JIRA)" 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HDFS-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802158#action_12802158 ] Eli Collins commented on HDFS-464: ---------------------------------- Looks like the patch just needs to be updated to address points 1 and 2 right? By the way it looks like all but four of these cases has been covered by patches Brian Bockelman has posted to various hdfs jiras. > Memory leaks in libhdfs > ----------------------- > > Key: HDFS-464 > URL: https://issues.apache.org/jira/browse/HDFS-464 > Project: Hadoop HDFS > Issue Type: Bug > Affects Versions: 0.20.1 > Reporter: Christian Kunz > Assignee: Christian Kunz > Priority: Blocker > Attachments: HADOOP-6034.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.