You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Julian Sedding (JIRA)" <ji...@apache.org> on 2016/04/22 14:45:13 UTC

[jira] [Commented] (OAK-4274) Memory-mapped files can't be explicitly unmapped

    [ https://issues.apache.org/jira/browse/OAK-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253855#comment-15253855 ] 

Julian Sedding commented on OAK-4274:
-------------------------------------

It may be possible to use {{PhantomReference}}s to {{MappedByteBuffer}}s so we can at least know when they have been garbage collected.

> Memory-mapped files can't be explicitly unmapped
> ------------------------------------------------
>
>                 Key: OAK-4274
>                 URL: https://issues.apache.org/jira/browse/OAK-4274
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: segment-next, segmentmk
>            Reporter: Francesco Mari
>             Fix For: 1.6
>
>
> As described by [this JDK bug|http://bugs.java.com/view_bug.do?bug_id=4724038], there is no way to explicitly unmap memory mapped files. A memory mapped file is unmapped only if the corresponding {{MappedByteBuffer}} is garbage collected by the JVM.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)