[
https://issues.apache.org/jira/browse/HADOOP-12958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212163#comment-15212163
]
Sangjin Lee commented on HADOOP-12958:
--------------------------------------
Thanks Jason!
One interesting side note: initially I was not able to reproduce it because I
was creating a Runnable (almost by instinct) and hanging the huge object there
and then created a thread with that Runnable. It turns out when a thread exits
it nulls out the Runnable, so that gets claimed no matter what. :) When I
switched to a thread without the Runnable, I was able to reproduce it.
Yet another reason a Runnable is better than a raw thread creation.
> PhantomReference for filesystem statistics can trigger OOM
> ----------------------------------------------------------
>
> Key: HADOOP-12958
> URL: https://issues.apache.org/jira/browse/HADOOP-12958
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.7.3, 2.6.4
> Reporter: Jason Lowe
> Assignee: Sangjin Lee
> Fix For: 2.7.3, 2.6.5
>
> Attachments: HADOOP-12958.01.patch
>
>
> I saw an OOM that appears to have been caused by the phantom references
> introduced for file system statistics management. I'll post details in a
> followup comment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
