Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Generic steps to identify a memory leak

DZone's Guide to

Generic steps to identify a memory leak

· Java Zone ·
Free Resource

Distribute microservices between the private and public clusters, yet maintain bi-directional connectivity. Content provided by IBM Developer.

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

Use this tool to look at the contents of GitHub and classify code based on the programming language used.  Content provided by IBM Developer.

Topics:

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}