This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 70079 - Incorrect instrumentation filter used for profiling
Summary: Incorrect instrumentation filter used for profiling
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jiri Sedlacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-08 11:54 UTC by Jiri Sedlacek
Modified: 2007-02-20 18:08 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Sedlacek 2005-12-08 11:54:38 UTC 
When profiling CPU (predefined Application Performance), other instrumentation 
filter than selected in task combo may be used.

Steps to reproduce:

1/ Select predefined Application Performance / Entire or Part, choose 
instrumentation filter, for example Exclude Core Java Classes

2/ Select Custom Profiling, create new task for CPU profiling, click 
Customize... instrumentation filter and create/select other filterset than 
Exclude Core Java Classes, close both Customize Filter Sets and New Custom 
Profiling dialogs by clicking the OK button

3/ Select predefined Application Performance task again and start profiling. 
Instrumentation filter defined for custom profiling is used, although Exclude 
Core Java Classes filter is selected for profiling
Comment 1 Jiri Sedlacek 2005-12-08 13:02:53 UTC 
Fixed for M12.
Comment 2 ehucka 2006-10-09 12:09:44 UTC 
Verification of old issues.
Comment 3 Alexander Kouznetsov 2007-02-20 10:13:05 UTC 
Closing old issues
Comment 4 Alexander Kouznetsov 2007-02-20 18:08:08 UTC 
Reverting to original Target Milestone value changed by mistake. Sorry for
inconvenience.