How is object liveness tracked?

When profiling an application, the liveness status is tracked only for those objects whose allocation it previously registered. That is, it does not make heap snapshots like some other tools. Instead, it internally associates Java WeakReference with objects that it registered allocated. If you started object liveness profiling in the middle of program execution, or if you invoke the Reset Collected Results command while profiling, it is likely that you will not see all of the live objects that are on the heap of your target VM. However, when solving the most important problems that object liveness profiling addresses - allocating too many objects over time, and memory leaks - this is not a serious issue. In these situations it is more important to see how many objects the application allocates and garbage collects currently, rather than how many have been allocated long ago, perhaps even at application startup time.

Applies to: NetBeans 5.5/6.*

Platforms: All

Back to NetBeans IDE Profiling FAQs

Back to NetBeans User FAQs

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo