hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-799) libhdfs must call DetachCurrentThread when a thread is destroyed
Date Tue, 10 Jul 2012 17:52:36 GMT

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

Colin Patrick McCabe commented on HDFS-799:

bq. Patch looks good, testing?

I tested it by adding printfs to the tls initialization and destruction functions, and verifying
that they did what was required.  More thorough testing will be provided by HDFS-3606, once
it goes in.
> 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
>            Reporter: Christian Kunz
>            Assignee: Colin Patrick McCabe
>         Attachments: HDFS-799.001.patch, HDFS-799.003.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


View raw message