Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 13 Jul 2012 02:48:34 +0000 (UTC)
From: "Colin Patrick McCabe (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <771573481.46124.1342147714981.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (HDFS-799) libhdfs must call DetachCurrentThread
 when a thread is destroyed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Colin Patrick McCabe updated HDFS-799:
--------------------------------------

    Attachment: HDFS-799.007.patch

* remove unnecessary if statement
                
> libhdfs must call DetachCurrentThread when a thread is destroyed
> ----------------------------------------------------------------
>
>                 Key: HDFS-799
>                 URL: https://issues.apache.org/jira/browse/HDFS-799
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 2.0.0-alpha
>            Reporter: Christian Kunz
>            Assignee: Colin Patrick McCabe
>             Fix For: 2.0.1-alpha
>
>         Attachments: HDFS-799.001.patch, HDFS-799.003.patch, HDFS-799.004.patch, HDFS-799.005.patch, HDFS-799.007.patch
>
>
> Threads that call AttachCurrentThread in libhdfs and disappear without calling DetachCurrentThread cause a memory leak.
> Libhdfs should detach the current thread when this thread exits.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira