Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Tue, 18 Nov 2014 04:35:33 +0000 (UTC)
From: "Bernd Eckenfels (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12369265.1179151211000.521738.1416285333856@Atlassian.JIRA>
In-Reply-To: <JIRA.12369265.1179151211000@Atlassian.JIRA>
References: <JIRA.12369265.1179151211000@Atlassian.JIRA>
 <JIRA.12369265.1179151211719@arcas>
Subject: [jira] [Resolved] (VFS-142) Clear ThreadData after all streams are
 closed, fixes a memory leak
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/VFS-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bernd Eckenfels resolved VFS-142.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.1

Ok tested it: with remove() there is a leak of FileContentThreadData objects avoided (when fo.close() or fc.close() is used). However there is still a leak if one uses any of the streams and closes them all, but does not close fileObject or fileContent. Since i commited this change with this ID I will close it as fixed and keep VFS-309 open.

> Clear ThreadData after all streams are closed, fixes a memory leak
> ------------------------------------------------------------------
>
>                 Key: VFS-142
>                 URL: https://issues.apache.org/jira/browse/VFS-142
>             Project: Commons VFS
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Adam Heath
>            Assignee: Bernd Eckenfels
>             Fix For: 2.1
>
>         Attachments: fix_ThreadData-clear.patch, threadlocal_setNull_vs_remove_bug.patch
>
>
> After all streams are closed in FileContentThreadData, clear the ThreadLocal.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)