Cisco Bug: CSCut29478 - CSM client memory leakage in javaw.exe process
Last Modified
Nov 10, 2016
Products (1)
- Cisco Security Manager
Known Affected Releases
4.7(0)
Description (partial)
Symptom: Error message "Available memory is below the minimum threshold level" appeared after "Refresh Hit count" button pressed. Conditions: Customer has a problem with memory exhausted on CSM client PC. When he pressed "Refresh Hit count" button, the memory for javaw.exe process increased. I have recreated this behavior in the lab. Below my investigations: I have run CSM client on my PC and checked memory allocated for java. Initially it was 0,6Gig Then I press "Refresh Hit count" button and started to observe memory usage. The memory allocation for java was approximately the 0.6-0.7Gig up to 71% completed (Completed 4 phases out of 5) and then dramatically increased up to 1.9Gig. Then I press "Refresh Hit count" button once more time and started to observe memory usage. The memory allocation for java was approximately the 1.9-2.0Gig up to 71% completed (Completed 4 phases out of 5) and then dramatically increased up to 3.5Gig. Then I press "Refresh Hit count" button once more time and started to observe memory usage. The memory allocation for java was approximately the 3.5Gig up to 71% completed (Completed 4 phases out of 5) and then I have received our error message that he memory is over.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Status
- Severity
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases