Skip navigation.
Downloads | Product Documentation | Support

Using the JRockit Memory Leak Detector

# Help Us Improve JRockit

The Memory Leak Detector is designed to help developers more easily find memory leaks and to better understand critical points of program engineering. It provides an easy way to capture information about object type allocation statistics.

If you have any suggestions about how to improve this tool or information on how it is most commonly used in development environments, we would be grateful to receive your input. This information would contribute to our understanding on how to best further improve this tool in the future.

Please, send an email with feedback and your ideas on how to use it to:

jrockit-improve@bea.com

# How will BEA Systems Use This Feedback

The feedback will be considered by the development team designing the Memory Leak Detector. We will look at collected ideas and improve the tools of BEA JRockit to make them even easier to use. Our goal with the development of this tool is to simplify the difficult task of finding memory leaks and help developers work more efficiently.

BEA JRockit is already providing a lot of appreciated manageability tools and, to keep a close dialogue with developers using Java Runtime Environments, BEA Systems is always trying to find ways to improve BEA JRockit. This is one of the ways.

# BEA JRockit Support for the Memory Leak Detector

Only more recent versions of BEA JRockit fully support the stand-alone Memory Leak Detector: BEA JRockit 5.0 sp1 and sp2.

# Frequently Asked Questions

Following are some questions we have frequently been asked about the Memory Leak Detector:

- Does BEA Systems Guarantee the Accuracy of this tool's output?
- Does the Memory Leak Detector Cause Any Overhead?
- What Kind of Support is Available for the Memory Leak Detector?
- Is There a Forum Where I can Discuss the Memory Leak Detector?

## Does BEA Systems Guarantee the Accuracy of this tool's output?

Since this is not a supported product, we cannot make any guarantees about the accuracy of the data shown or the stability of JRockit when using the Memory Leak Detector.

## Does the Memory Leak Detector Cause Any Overhead?

In the trend analysis of the memory leak detection process, the data presented is continuously updated; however, the overhead during this phase is very small. Each garbage collection will take a bit longer. During the second and third phase the only overhead will be some additional garbage collections, which in most cases is negligible. Overall, there is practically no overhead and it should not affect the speed or results of your application.

## What Kind of Support is Available for the Memory Leak Detector?

The Memory Leak Detector functionality is currently being provided as-is for your convenience and to help with memory leak detection and is not supported by BEA Support.

## Is There a Forum Where I can Discuss the Memory Leak Detector?

If you have any questions you are welcome to share them in the BEA JRockit general interest newsgroup, which is monitored by our engineering team. To access the newsgroup, go to:

http://newsgroups.bea.com

# Known Issues

Sometimes static fields and the number of thread roots are not correctly displayed in the window displaying instances referring to an other instance. You can fix this by starting the memory leak detection process once again (that is, unfreezing and freezing the memory leak system); however, any data displayed is correct.