commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernd Eckenfels (JIRA)" <>
Subject [jira] [Commented] (VFS-545) DefaultFilesCache leaks closed filesystems
Date Wed, 12 Nov 2014 18:20:34 GMT


Bernd Eckenfels commented on VFS-545:

My idea would be to simply use

    public void clear(FileSystem filesystem)
        Map<FileName, FileObject> files = filesystemCache.remove(filesystem);
        files.clear(); // help GC

> DefaultFilesCache leaks closed filesystems
> ------------------------------------------
>                 Key: VFS-545
>                 URL:
>             Project: Commons VFS
>          Issue Type: Bug
>    Affects Versions: 2.0, 2.1
>            Reporter: Bernd Eckenfels
>            Assignee: Bernd Eckenfels
>            Priority: Minor
>              Labels: leak
> The org.apache.commons.vfs2.cache.DefaultFilesCache does not remove the filesystem specific
cache if a filesystem gets cleared. This leads to the problem that instances if the FileSystem
kept alive after the FileProvider has closed the filesystem. This is not so much a problem
for a smaller number of filesystems configured for a prefix, but it is a problem for layered
or virtual filesystems which get created and destroyed. (See also VFS-544). The more advanced
filesystem caches support clearing the keys (but have other races I think).
> The behaviour is somewhat documented "lifetime of the FileSystemManager", but I don't
think it is expected or required.

This message was sent by Atlassian JIRA

View raw message