cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9564) Fix memory leak in VmwareContextPool
Date Tue, 06 Dec 2016 06:09:58 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15724487#comment-15724487
] 

ASF GitHub Bot commented on CLOUDSTACK-9564:
--------------------------------------------

Github user rhtyd commented on the issue:

    https://github.com/apache/cloudstack/pull/1816
  
    LGTM, merging this on last TravisCI's first job result. Only the first job runs/builds
with unit tests.


> 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)

Mime
View raw message