[
https://issues.apache.org/jira/browse/CLOUDSTACK-9564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15605126#comment-15605126
]
ASF GitHub Bot commented on CLOUDSTACK-9564:
--------------------------------------------
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/1729
@rhtyd I understand these words: "help", "hello", "thanks", "package",
"test"
Test run usage: test (mgmt server, one of: centos6, centos7, ubuntu)
(hypervisor, one of: kvm-centos6, kvm-centos7, kvm-ubuntu, xenserver-65sp1,
xenserver-62sp1, vmware-60u2, vmware-55u3, vmware-51u1, vmware-50u1)
Authorized contributors for kicking Trillian Jenkins test jobs are:
['rhtyd', 'jburwell', 'murali-reddy', 'abhinandanprateek', 'PaulAngus',
'borisstoyanov', 'karuturi']
> Fix memory leak in VmwareContextPool
> ------------------------------------
>
> Key: CLOUDSTACK-9564
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9564
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
>
> In a recent management server crash, it was found that the largest
> contributor to memory leak was in VmwareContextPool where a registry is held
> (arraylist) that grows indefinitely. The list itself is not used anywhere or
> consumed. There exists a hashmap (pool) that returns a list of contexts for
> existing poolkey (address/username) that is used instead. The fix would be to
> get rid of the registry and limit the hashmap context list length for any
> poolkey.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
