Preview Tool

Cisco Bug: CSCvh84127 - ASDM navigation slow about 1 hour after session is established

Last Modified

Sep 16, 2019

Products (1)

  • Cisco Adaptive Security Device Manager

Known Affected Releases


Description (partial)

ADSM navigation in between options start to present considerably delay some time after ASDM is established.

On Lab, issue was seen about 1 hour after initial connection, but this may vary.

Issue seems to be a result of either memory leak/continuous usage of more RAM memory by javaw.exe or jp2launcher.exe process on windows client pc.

On tests executed the RAM used by process above mentioned is about twice higher as compared of when the ASDM session is started after authentication.

Issue is also seen when moving in between options that do not result on command execution on the ASA side, such as changing in between "Home" and "Configuration" or simply minimizing and maximizing back the ASDM window

Issue was seen on following platforms:

FPR4K-SM-36 / ASA /
ASDM Releases,
FXOS 2.2.2 and 2.2.1
Java Releases 1.8 and 1.7

Issue is likely to affect ASDM sessions to any ASA model (whether Hardware of Software based) as issue lands on ASDM and/or Java domain
Bug details contain sensitive information and therefore require a 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
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.