[jira] Commented: (HADOOP-4635) Memory leak ?

["Marc-Olivier Fleury (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646648#action_12646648 ] 

Marc-Olivier Fleury commented on HADOOP-4635:
---------------------------------------------

After some further testing, I notified that the amount of memory used by fuse_dfs is of about 70MB (varies from a machine to the other).

I tried to use vmstat to see if a lot of paging was involved, and it does not seem to be the case.

I might just have done a report for an unexisting bug, I apologize if it is the case, an am in any way ready to do as many tests as needed to get a better understanding of the situation.

> Memory leak ?
> -------------
>
>                 Key: HADOOP-4635
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4635
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/fuse-dfs
>    Affects Versions: 0.20.0
>            Reporter: Marc-Olivier Fleury
>
> I am running a process that needs to crawl a tree structure containing ~10K images, copy the images to the local disk, process these images, and copy them back to HDFS.
> My problem is the following : after about 10h of processing, the processes crash, complaining about a std::bad_alloc exception (I use hadoop pipes to run existing software). When running fuse_dfs in debug mode, I get an outOfMemoryError, telling that there is no more room in the heap.
> While the process is running, using top or ps, I notice that fuse is using up an increasing amount of memory, until some limit is reached. At that point , the memory used is oscillating. I suppose that this is due to the use of the virtual memory.
> This leads me to the conclusion that there is some memory leak in fuse_dfs, since the only other programs running are Hadoop and the existing software, both thoroughly tested in the past.
> My problem is that my knowledge concerning memory leak tracking is rather limited, so I will need some instructions to get more insight concerning this issue.
> Thank you

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.