You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Arun C Murthy (JIRA)" <ji...@apache.org> on 2012/10/11 19:46:52 UTC
[jira] [Closed] (HDFS-799) libhdfs must call DetachCurrentThread
when a thread is destroyed
[ https://issues.apache.org/jira/browse/HDFS-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy closed HDFS-799.
------------------------------
> 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.2-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
For more information on JIRA, see: http://www.atlassian.com/software/jira