[
https://issues.apache.org/jira/browse/VFS-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14211813#comment-14211813
]
Bernd Eckenfels edited comment on VFS-544 at 11/14/14 4:50 AM:
---------------------------------------------------------------
I commited some cleanup work on trunk, v2 patch is against the cleaned up
version. It makes VirtualFileProvider a dynamically managed resource. It also
makes sure closeFilesystem is passed to VirtualFileProvider.
was (Author: b.eckenfels):
I commited some cleanup work on trunk, this patch is against the cleaned up
version. It makes VirtualFileProvider a dynamically managed resource. It also
makes sure closeFilesystem is passed to VirtualFileProvider.
> 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)
