commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernd Eckenfels (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (VFS-544) VirtualFileSystems leak
Date Wed, 19 Nov 2014 03:59:34 GMT

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

Bernd Eckenfels resolved VFS-544.
---------------------------------
    Resolution: Fixed

Ok, I have commited a fix:

http://svn.apache.org/r1640477

> 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-v2.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)

Mime
View raw message