[ https://issues.apache.org/jira/browse/GEODE-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16173595#comment-16173595 ]
ASF subversion and git services commented on GEODE-3314: -------------------------------------------------------- Commit 26a414582bc718f19a2a94c741132f17bc4ebe53 in geode's branch refs/heads/master from [~gosullivan] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=26a4145 ] GEODE-3314 - Refactoring of DLockService to improve developer QoL. This now closes #683 * Write characterization tests for DLockService. * Remove debugging code. * Remove dead code. * Remove comments. * Extract the local lock granting into a separate function. Between the characterization tests we've written and the existing DUnit tests, the coverage should be fairly adequate. Signed-off-by: Hitesh Khamesra <hkames...@pivotal.io> Signed-off-by: Galen O'Sullivan <gosulli...@pivotal.io> (cherry picked from commit 190cfed880da17b947eb520948866062b9aafe0b) > OldGen heap usage grows without increase in data size, large number of > DLockTokens > ---------------------------------------------------------------------------------- > > Key: GEODE-3314 > URL: https://issues.apache.org/jira/browse/GEODE-3314 > Project: Geode > Issue Type: Bug > Components: distributed lock service > Reporter: Udo Kohlmeyer > Assignee: Galen O'Sullivan > Fix For: 1.2.1 > > > When using Global Replicate regions, the DLockTokens are not correctly > cleaned up, causing a memory leak. -- This message was sent by Atlassian JIRA (v6.4.14#64029)