Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ECC531768C for ; Wed, 12 Nov 2014 08:54:33 +0000 (UTC) Received: (qmail 88750 invoked by uid 500); 12 Nov 2014 08:54:33 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 88656 invoked by uid 500); 12 Nov 2014 08:54:33 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 88644 invoked by uid 99); 12 Nov 2014 08:54:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Nov 2014 08:54:33 +0000 Date: Wed, 12 Nov 2014 08:54:33 +0000 (UTC) From: "Bernd Eckenfels (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (VFS-544) VirtualFileSystems leak MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/VFS-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Eckenfels updated VFS-544: -------------------------------- Attachment: vfs-544-v1.patch First version of the patch, it passes all tests (on Windows). > VirtualFileSystems leak > ----------------------- > > Key: VFS-544 > URL: https://issues.apache.org/jira/browse/VFS-544 > Project: Commons VFS > Issue Type: Bug > Affects Versions: 2.0 > Reporter: Bernd Eckenfels > Assignee: Bernd Eckenfels > Labels: leak, patch > Fix For: 2.1 > > Attachments: vfs-544-v1.patch > > > When creating a org.apache.commons.vfs2.impl.VirtualFileSystem by org.apache.commons.vfs2.impl.VirtualFileProvider it is tracked as a component. But since VirtualFileProvider is not an AbstractFileProvider and not registered in providers it will never be closed by org.apache.commons.vfs2.impl.DefaultFileSystemManager._closeFileSystem(FileSystem). Also the final instance of VirtualFileProvider does not get closed when the DefaultFileSystemManager gets closed. > VirtualFileSystem itself does not have critical resources, but its DelegatedFiles are cached so there should be a way to close them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)