Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 200367

Summary: Profiling type doesn't change
Product: z_Archived Reporter: Alexander N. Alexeev <analexee>
Component: TPTPAssignee: Igor Alelekov <igor.alelekov>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P1 CC: analexee, jkubasta
Version: unspecifiedKeywords: plan
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: closed460

Description Alexander N. Alexeev CLA 2007-08-17 10:08:28 EDT
Build ID: 3.3

Steps To Reproduce:
1. Open "Profile dialog"
2. Create profiling for Simples Java application (call "simple") 
3. Go to "Monitor" tab and choose "Thread Analysis" in "JRE 1.5. or newer"
4. Press "profile"
5. Open again "Profile dialog" and choose "simple" configuration
6. Go to Monitor tab and change profiling type from "Thread Analysis" to "Memory Analysis" (apply button still disabled)
7. Go to "Edit option" button and change "level of detail" box
8. Go out, press "apply" (now enabled) and "profile"

With big probability "Thread Analysis" will be executed instead of "Memory Analysis"


More information:
Comment 1 Igor Alelekov CLA 2008-01-25 07:38:32 EST
Alex, I can't reproduce the defect.
Please check any last dev. build, the bug might be fixed with #200533.
Comment 2 Alexander N. Alexeev CLA 2008-01-30 06:56:04 EST
This problem cannot be reproduced on TPTP build 4.5.0-200801281200
Comment 3 Igor Alelekov CLA 2008-01-30 07:00:50 EST
Resolving as fixed
Comment 4 Paul Slauenwhite CLA 2009-06-30 13:45:46 EDT
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.
Comment 5 Paul Slauenwhite CLA 2009-06-30 14:18:43 EDT
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.