[
https://issues.apache.org/jira/browse/OAK-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253795#comment-15253795
]
Francesco Mari commented on OAK-4211:
-------------------------------------
The current implementation of {{FileAccess.Mapped}} might have another problem
regarding the way memory mapped files are unmapped. Every time a read operation
is performed on {{FileAccess.Mapped}}, we create a slice of the
{{MappedByteBuffer}} that references the original buffer. This means that we
(indirectly) expose a reference to the {{MappedByteBuffer}} to client code,
with the potential of impacting the unmapping of the memory mapped files that
we open.
> FileAccess.Mapped leaks file channels
> --------------------------------------
>
> Key: OAK-4211
> URL: https://issues.apache.org/jira/browse/OAK-4211
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-next
> Reporter: Michael Dürig
> Fix For: 1.6
>
> Attachments: OAK-4211-02.patch, OAK-4211.patch
>
>
> {{FileAccess.Mapped}} seems to leak {{FileChannnel}} instances. The file
> channels are acquired in the constructor but never release.
> FYI [~alex.parvulescu], [~frm]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
