Community
Participate
Working Groups
In Profile Launch configuration, Memory/Leak Analysis and Execution right pane, the “show instance level info” checkbox needs to have a description of which views it enables, at what cost of collection speed/size.
Would the following cover what users would most likely use this option for? (For the memory analysis) [] Collect instance information for memory leak analysis. Note: If the Collect Object Reference action is used with this option, data is collected for all active objects pointing to and from the filtered classes. (For execution analysis) [] Collect all instance level data. (Do you have the same problem with the application hanging if this is selected for execution analysis? If so, we could add a note here as well).
I think that the description should include the fact that the amount of data collected in this cases grows exponential relatively to the number of classes collected ( one class can have a huge number of instances, such as the String class ). Yes, the same performance problem results when collect instance information when execution flow is selected
Adding documentation keyword
Sorry.. accidentally closed the bug.
Now that we have a "3.3" Version in bugzilla, updating bugzillas targeted to 3.3 or a 3.3 iteration so that their Version matches their Target. "future", "unspecified", "4.0", and "4.1" Versions will not be updated.
Updated the following in 3.3 & 4.0: - specifying profiling criteria - identifying memory leaks - running garbage collection
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.
