Over a million developers have joined DZone.

Generic steps to identify a memory leak

· Java Zone

Discover how AppDynamics steps in to upgrade your performance game and prevent your enterprise from these top 10 Java performance problems, brought to you in partnership with AppDynamics.

1. Start the application with profiler options enabled.

2. Run Garbage Collector using profiler client tool.

3. Capture memory snapshot.

4. Submit request to the server application.

5. Once the job has run successfully run GC again.

6. Capture memory snapshot.

7. Compare snapshots to find if any objects are leaked.

Repeat Steps 4 to 7 with similar request.If you find an increase in memory after each successive request completion then memory leak can be suspected. Then the suspect objects can be found out by analyzing report like dominator tree objects etc and probably code fix might be necessary to prevent memory leak. Once the code fix is done, you can repeat the steps mentioned above to see if the fix has helped to resolve memory leak.

Sharath.H

The Java Zone is brought to you in partnership with AppDynamics. AppDynamics helps you gain the fundamentals behind application performance, and implement best practices so you can proactively analyze and act on performance problems as they arise, and more specifically with your Java applications. Start a Free Trial.

Topics:

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}