Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 85113 invoked from network); 18 Nov 2008 22:24:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Nov 2008 22:24:08 -0000 Received: (qmail 80605 invoked by uid 500); 18 Nov 2008 22:24:13 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 80571 invoked by uid 500); 18 Nov 2008 22:24:13 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 80553 invoked by uid 99); 18 Nov 2008 22:24:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Nov 2008 14:24:13 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Nov 2008 22:22:59 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5CC85234C293 for ; Tue, 18 Nov 2008 14:23:44 -0800 (PST) Message-ID: <1529512991.1227047024378.JavaMail.jira@brutus> Date: Tue, 18 Nov 2008 14:23:44 -0800 (PST) From: "Marc-Olivier Fleury (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-4635) Memory leak ? In-Reply-To: <114129394.1226431904287.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648783#action_12648783 ] Marc-Olivier Fleury commented on HADOOP-4635: --------------------------------------------- I am using the latest patch provided in issue HADOOP-4616, which is supposed to fix the leaks, and I have bad news: there are still leaks. while searching through the code, I noticed taht some of the functions used as fuse_operations are not static. Can it be a problem? At least, fixing this does not remove the leak. I am running a version using static functions, the leak is still there. I am running out of clues, so any help would be appreciated. Thanks! > 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.19.0, 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.