[
https://issues.apache.org/jira/browse/VFS-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14215263#comment-14215263
]
Bernd Eckenfels edited comment on VFS-142 at 11/17/14 10:09 PM:
----------------------------------------------------------------
Ah stupid me... I reverse-read the patch. Yes remove is better than set :) (But
I don't think it explains a leak).
Will commit it. But I need to check if this actually fixes the bug - especially
when FileContent.close() is not directly called.
was (Author: b.eckenfels):
Ah stupid me... I reverse-read the patch. Yes remove is better than set :) (But
I don't think it explains a leak).
Will commit it.
> Clear ThreadData after all streams are closed, fixes a memory leak
> ------------------------------------------------------------------
>
> Key: VFS-142
> URL: https://issues.apache.org/jira/browse/VFS-142
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: 1.1
> Reporter: Adam Heath
> Attachments: fix_ThreadData-clear.patch,
> threadlocal_setNull_vs_remove_bug.patch
>
>
> After all streams are closed in FileContentThreadData, clear the ThreadLocal.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
