You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Bernd Eckenfels (JIRA)" <ji...@apache.org> on 2014/11/12 09:17:33 UTC

[jira] [Created] (VFS-544) VirtualFileSystems leak

Bernd Eckenfels created VFS-544:
-----------------------------------

             Summary: 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
             Fix For: 2.1


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)