You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/09/21 22:35:00 UTC
[jira] [Commented] (GEODE-5772) fix the potential cache leak caused
by reconnect
[ https://issues.apache.org/jira/browse/GEODE-5772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16624260#comment-16624260 ]
ASF subversion and git services commented on GEODE-5772:
--------------------------------------------------------
Commit a92c904194f117ea5a14f63bf3c0bb211fd55572 in geode's branch refs/heads/feature/GEODE-5772 from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a92c904 ]
GEODE-5772: fix the potential cache leaks caused by reconnect
> fix the potential cache leak caused by reconnect
> ------------------------------------------------
>
> Key: GEODE-5772
> URL: https://issues.apache.org/jira/browse/GEODE-5772
> Project: Geode
> Issue Type: Bug
> Components: core
> Reporter: xiaojian zhou
> Priority: Major
>
> Customer reported when reconnect happens, the memory usage will increase a lot.
>
> After investigation with Barry and Anil, we found there're one or more cache instances are still alive after reconnect closed it and created a new live cache.
>
> We walk through the code and fix some potential places that still hold the cache reference.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)