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

Bug 200532

Summary:	Data about system classes is collected with "Default" filters
Product:	z_Archived	Reporter:	Alexander N. Alexeev <analexee>
Component:	TPTP	Assignee:	Igor Alelekov <igor.alelekov>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P1	CC:	analexee, asaf.yaffe, igor.alelekov, jkubasta
Version:	unspecified	Keywords:	plan
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	closed460

Description Alexander N. Alexeev

2007-08-20 06:59:40 EDT

Build ID: 3.3

Steps To Reproduce:
Build ID: 3.3

Steps To Reproduce:
1. Create simple "Hello world" java application
2. Open "Profile dialog"
3. Profile "Hello world" application as "Java application"
4. Go to Monitor tab
5. Choose "JRE1.5 or newer" 
6. Click "Edit option" and choose "Default" predefined filter and press "Finish"
7. Select "Memory Analysis"
8. Press profile 

Don't forget at "Memory statistic" view select "no filter" at filter options

classes from java.lang, java.util, sun.misc, java.io will be in view in spite of the fact that they all should be excluded from collecting

Comment 1 Asaf Yaffe

2007-08-20 09:49:38 EDT

*** Bug 200371 has been marked as a duplicate of this bug. ***

Comment 2 Asaf Yaffe

2007-08-20 09:52:19 EDT

To reproduce, make sure to enable the "track object allocation sites" option of the Heap profiler.

Comment 3 Asaf Yaffe

2007-08-20 09:56:44 EDT

Root-cause analysis: first, note that the "unwanted classes" (e.g. the filtered-out classes) always appear with "0" in all allocation statistics columns.

The entries for these classes appear as a result of <classDef> elements which are generated for the allocation site information. 

To fix this, make sure that classes without any allocation statistics (e.g., no <objAlloc> events) do not appear in the view.

Comment 4 Asaf Yaffe

2007-08-20 09:57:22 EDT

Changed "version" field to 4.4, as this bug was found in TPTP 4.4.

Comment 5 Igor Alelekov

2007-12-20 08:54:35 EST

(In reply to comment #3)
> Root-cause analysis: first, note that the "unwanted classes" (e.g. the
> filtered-out classes) always appear with "0" in all allocation statistics
> columns.
> The entries for these classes appear as a result of <classDef> elements which
> are generated for the allocation site information. 
> To fix this, make sure that classes without any allocation statistics (e.g., no
> <objAlloc> events) do not appear in the view.

Asaf, are you suggesting to screen such classes in the workbench view?
Can we do it in the jvmti runtime - don't send <classDef> elements for classes without allocation statistics?

Comment 6 Asaf Yaffe

2007-12-20 09:23:30 EST

(In reply to comment #5)
> 
> Asaf, are you suggesting to screen such classes in the workbench view?
> Can we do it in the jvmti runtime - don't send <classDef> elements for classes
> without allocation statistics?
> 

I think we have no choice but to do the screening in the workbench side. The <classDef> elements in question (the ones that do not have allocation information) are still required to properly populate the model and the Allocation Sites view (you can't have a <methodDef> element without its <classDef> element).

Comment 7 Igor Alelekov

2008-04-07 02:07:18 EDT

Fixed.

Comment 8 Paul Slauenwhite

2009-06-30 13:45:49 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 9 Paul Slauenwhite

2009-06-30 14:20:02 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.