cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9564) Fix memory leak in VmwareContextPool
Date Tue, 06 Dec 2016 06:27:58 GMT


ASF subversion and git services commented on CLOUDSTACK-9564:

Commit dcbf3c8689ed3eaed8653763ec27d2907671c72b in cloudstack's branch refs/heads/4.9 from
[;h=dcbf3c8 ]

CLOUDSTACK-9564: Fix NPE due to intermittent test assertion

The test assertion on a pool object may return a null object, as objects
can be randomly expired/tombstoned. This will fix a NPE sometimes seen due
to recently merge for the fix for CLOUDSTACK-9564.

Signed-off-by: Rohit Yadav <>

> Fix memory leak in VmwareContextPool
> ------------------------------------
>                 Key: CLOUDSTACK-9564
>                 URL:
>             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

View raw message