You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Sergey Vladimirov (JIRA)" <ji...@apache.org> on 2008/12/05 21:06:44 UTC
[jira] Created: (VFS-227) InputStream and RandomAccessContent
memory leak in FileContentThreadData
InputStream and RandomAccessContent memory leak in FileContentThreadData
------------------------------------------------------------------------
Key: VFS-227
URL: https://issues.apache.org/jira/browse/VFS-227
Project: Commons VFS
Issue Type: Bug
Affects Versions: Nightly Builds
Environment: doesn't seem to be fixed in SVN
Reporter: Sergey Vladimirov
Memory leak can be found by opening and closing input stream for the same file several thouthand times.
Thanks to Nikita Ershov for invistigation and solution
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (VFS-227) InputStream and RandomAccessContent
memory leak in FileContentThreadData
Posted by "Sergey Vladimirov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VFS-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Vladimirov updated VFS-227:
----------------------------------
Attachment: patch.txt
> InputStream and RandomAccessContent memory leak in FileContentThreadData
> ------------------------------------------------------------------------
>
> Key: VFS-227
> URL: https://issues.apache.org/jira/browse/VFS-227
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: Nightly Builds
> Environment: doesn't seem to be fixed in SVN
> Reporter: Sergey Vladimirov
> Attachments: patch.txt
>
>
> Memory leak can be found by opening and closing input stream for the same file several thouthand times.
> Thanks to Nikita Ershov for invistigation and solution
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (VFS-227) InputStream and RandomAccessContent
memory leak in FileContentThreadData
Posted by "Sergey Vladimirov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VFS-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658040#action_12658040 ]
Sergey Vladimirov commented on VFS-227:
---------------------------------------
Thinking if i should ask for svn write access to apply this trivial patch by myself...
> InputStream and RandomAccessContent memory leak in FileContentThreadData
> ------------------------------------------------------------------------
>
> Key: VFS-227
> URL: https://issues.apache.org/jira/browse/VFS-227
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: Nightly Builds
> Environment: doesn't seem to be fixed in SVN
> Reporter: Sergey Vladimirov
> Attachments: patch.txt
>
>
> Memory leak can be found by opening and closing input stream for the same file several thouthand times.
> Thanks to Nikita Ershov for invistigation and solution
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (VFS-227) InputStream and RandomAccessContent
memory leak in FileContentThreadData
Posted by "Ralph Goers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VFS-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers resolved VFS-227.
-----------------------------
Resolution: Fixed
Fix Version/s: 2.0
The patch was applied to trunk. Please verify and close.
> InputStream and RandomAccessContent memory leak in FileContentThreadData
> ------------------------------------------------------------------------
>
> Key: VFS-227
> URL: https://issues.apache.org/jira/browse/VFS-227
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: Nightly Builds
> Environment: doesn't seem to be fixed in SVN
> Reporter: Sergey Vladimirov
> Fix For: 2.0
>
> Attachments: patch.txt
>
>
> Memory leak can be found by opening and closing input stream for the same file several thouthand times.
> Thanks to Nikita Ershov for invistigation and solution
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.