1. Administration Guide
  2. Use Case 1

Use Case 1

If an Application is known to have a memory leak:

  1. Launch the Application to the App Entry point.

  2. Associate the Application to a given CallObject by correlating under "Remote Env" section of HTML WebSessions.

  3. Drill into the Callobject Kernel and click on "Start JADE" Button.

  4. Execute the pre-defined transactions on the application.

  5. When done, click on "Dump JADE" Button.

  6. Exit the Application and click on "Stop JADE" Button.

  7. Click "Parse JADE" to see the possible leak locations.

In the previous use case we can determine if there is any unallocated memory at the end of Application's run. If yes, then it can be determined from where it is being allocated.