You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mnemonic.apache.org by "Wang, Gang (JIRA)" <ji...@apache.org> on 2017/03/03 21:09:45 UTC

[jira] [Commented] (MNEMONIC-215) Memory leak when LinkedList element is destroyed

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

Wang, Gang commented on MNEMONIC-215:
-------------------------------------

Yes it is true, It would leak next nodes if the next nodes not yet accessed for restoring, Thanks Johnu.

> Memory leak when LinkedList element is destroyed
> ------------------------------------------------
>
>                 Key: MNEMONIC-215
>                 URL: https://issues.apache.org/jira/browse/MNEMONIC-215
>             Project: Mnemonic
>          Issue Type: Bug
>            Reporter: Johnu George
>            Assignee: Wang, Gang
>            Priority: Critical
>             Fix For: 0.6.0-incubating
>
>
> Here is the implementation of the destroy function in LinkedList node
>   @Override
>   public void destroy() throws RetrieveDurableEntityError {
>     m_holder.destroy();
>     if (null != m_item) {
>       m_item.destroy();
>       m_item = null;
>     }
>     if (null != m_next) {
>       m_next.destroy();
>       m_next = null;
>     }
>   }
> Next is destroyed only when m_next is not null. m_next can also be null if next item is not loaded into memory from PMem. It is required to first restore the item using getNext and then call destroy. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)