[
https://issues.apache.org/jira/browse/HADOOP-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646706#action_12646706
]
Marc-Olivier Fleury commented on HADOOP-4635:
---------------------------------------------
Great, I see that you have some good ideas on what parts of the code should
cause issues.
I am using the latest version from svn, 0.20.0, I think. (had to upgrade to be
able to use the writing functionalities)
I spent some time looking at the code, and I noticed a strange little quirk
(fuse_dfs.c:608). The '+1' in the malloc. I don't get why it is there, must be
a relic... it is not important, since it will be freed anyway, still...
Anyway, I am chasing the leaks right now and I am happy to see that some of the
leaks are already located. Is the hdfsConnectAsUser difficult to fix? I will
take a look and try to fix it, but if you have any insight, pleease let me know!
> 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.
