Memory Profiling for Java

Run-time memory problems are among the most difficult errors to locate and the most important to correct. The symptoms of incorrect memory use are unpredictable and typically appear far from the cause of the error. The issue often remain undetected until triggered by a random event, so that a program can seem to work correctly when in fact it's only working by accident.

That's where the Memory Profiling feature can help you get ahead.

You associate Memory Profiling with an existing test node or Application code.
You compile and run your application.
The application with the Memory Profiling feature, then directs output to the Memory Profiling Viewer, which provides a detailed report of memory issues.

The Java version of Memory Profiling differs from other programming languages, among other aspects, by the way memory is managed by the Java Virtual Machine (JVM). The technique used is the JVMPI Agent technology for Java.

Memory Profiling for Java supports JDK 1.3.x and JDK 1.4.x

C++: ISO/IEC 14882:1998

How Memory Profiling for Java Works

When an application node is executed, the source code is executed. The Memory Profiling for Java feature uses the JVMPI mechanism to monitor the application. JVMPI outputs a dynamic .jpt file.

The .jpt file is split into a .tpf file and a .txf file, which can be viewed and controlled from the HCL OneTest™ Embedded GUI. Both the .tpf and .txf files need to be opened simultaneously to view the report.

Of course, these steps are mostly transparent to the user when the test or application node is executed in the HCL OneTest™ Embedded GUI.


To learn about	See
Performing Memory Profiling on C, C++ and Java source code	Using Runtime Analysis Features
JVMPI technology for Java memory analysis	JVMPI Technology
Understanding Memory Profiling Reports	Memory Profiling Results for Java
Viewing the Memory Profiling reports for Java	Using the Report Viewer
Customizing the Memory Profiling Viewer	Memory Profiling Viewer Preferences