Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Memory Analysis

Revision as of 09:27, 8 October 2008 by Unnamed Poltroon (Talk) (New page: == Memory Analysis : Identify a memory leak == Memory leak problem can be identify with the help of Memory Analysis. Memory Analysis can be enabled in the launch configuration by selecti...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Memory Analysis : Identify a memory leak

Memory leak problem can be identify with the help of Memory Analysis. Memory Analysis can be enabled in the

launch configuration by selecting Memory Analysis type of a Java profiler.

Sanp23.jpg

If allocation detail information is required, enable the Track Object Allocation Site option in the

Edit Option detail of the analysis type.

Sanp24.jpg

Double-clicking on the profile agent opens the Memory Statistics view which shows memory related

information of an application under profiled.

Sanp26.jpg

Selecting any class instance in the table and switch to the Allocation Details tab gives more

information about the allocation of the selected class. Note that allocation details is available only when

Track Object Allocation Site option is enabled in the profile configuration.

Sanp27.jpg

In the view, array information is also traced. They are shown as type[] for array or type[][] for two-

dimensional array and so on.

Sanp28.jpg



Return to the Profiling with TPTP - plug-in developmeet page.

Back to the top