[OAK-3199] DocumentNodeState ignores binary value for memory calculation

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.18, 1.2.3
• Fix Version/s: 1.0.19, 1.2.4, 1.3.4, 1.4
• Component/s: core, mongomk
• Assignee: Marcel Reutegger
• Reporter: Marcel Reutegger
• Created: 10/Aug/15 07:24
• Updated: 02/Mar/16 12:00
• Resolved: 12/Aug/15 14:41

Description

DocumentNodeState ignores memory usage of a binary PropertyState because it assumes the value is in the blob store. Even if the value is in the blob store, the PropertyState still contains a blob reference as its value, which must be considered for the memory calculation.

A cache of DocumentNodeState instances may use considerably more memory than assigned when there are many binary PropertyStates.