[MNEMONIC-215] Memory leak when LinkedList element is destroyed

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 0.6.0-incubating
• Assignee: Johnu George
• Reporter: Johnu George
• Created: 03/Mar/17 20:34
• Updated: 27/Mar/17 21:06
• Resolved: 27/Mar/17 21:06

Description

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.

Issue Links

• links to: GitHub Pull Request #32