Community
Participate
Working Groups
The most common reason why profilers are used is to detect memory leaks. TPTP doesn’t currently offer a convincing set of views and analysis tools for detecting memory leaks. The purpose of this feature is to list the enhancements that need to be made to make memory leak detection easier. Some changes listed below may require the runtime to provide added functionality: - The look and feel of the object reference view needs to be changed. It provides a flat look that is hard to navigate through. It does a poor job in providing the visual overview of object references - Objects that are garbage collected need to be removed from the object reference view. Data is only accumulated in this view making analysis very difficult or almost impossible. - It may even make sense to integrate the object reference view with the memory statistics view. We currently offer instance level information under memory stat view. We can use this view to also display references that are holding to an instance. - It’s difficult to determine why an object is not garbage collected. In the object reference view you will often hit dead ends when trying to find references to an object. - Provide a dynamic chart that is updated when the heap size changes (very much like XRay)
investigate for 4.3
*** This bug has been marked as a duplicate of 141336 ***
sorry, marked wrong bug
Per Profiling and Trace call on Jul 31th, targeting to future, candidate of 4.3.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html).
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
