[ https://issues.apache.org/jira/browse/GEODE-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16537788#comment-16537788 ]
ASF subversion and git services commented on GEODE-5292: -------------------------------------------------------- Commit 9037d42bf291b504fea98bff4c851aac15e0625c in geode's branch refs/heads/develop from Dan Smith [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9037d42 ] [GEODE-5292] Actually destroy the region instead of pretending to. Signed-off-by: Dan Smith <dsm...@pivotal.io> > Replace with concurrent clear and destroy leaks off heap memory > --------------------------------------------------------------- > > Key: GEODE-5292 > URL: https://issues.apache.org/jira/browse/GEODE-5292 > Project: Geode > Issue Type: Bug > Components: regions > Reporter: Dan Smith > Assignee: Dan Smith > Priority: Major > Labels: pull-request-available, swat > Fix For: 1.8.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > For a region that has been configured with off-heap storage and overflow to > disk, memory can be leaked if > * region clear > * region destroy > * region replace > all happen concurrently. The root cause appears to be region clear modifying > entries for values stored on disk without synchronizing the entries. This > prevents replace from freeing the off-heap memory for the new value when the > replace fails because the region is being destroyed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)