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 237703 - Method name filter (Contains) in profiler does not work as expected (filters out everything)
Summary: Method name filter (Contains) in profiler does not work as expected (filters ...
Status: RESOLVED INVALID
Alias: None
Product: profiler
Classification: Unclassified
Component: Ide (show other bugs)
Version: 7.4
Hardware: PC Windows 8 x64
: P3 normal (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-27 20:48 UTC by mimkorn
Modified: 2013-10-27 20:51 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mimkorn 2013-10-27 20:48:12 UTC
I might not understand the functionality correctly, but I believe, that it should filter out methods that contain somewhere in the name things that I type into the field. 

CPU Profile any project, take a snapshot during the run and under the data put something in the field, where it's written Method Name Filter. 

While I was writing this bug I tested some stuff and realized, that it always filters out everything, even methods, that should pass the filter, IF they are inside a method, which does not pass the filter. Is this supposed to happen? This way one can only filter out the top level methods and everything inside these methods, that does not pass the filter. I would expect to be able to go the other way around, from the bottom of the stack trace up. If the methods inside a method are filtered out, okay, but if one of the methods passes the filter, it stays highlighted, within its stack trace (even though the stack would constitue methods, which would not pass the filter - they would not be highlighted or so...)
Comment 1 mimkorn 2013-10-27 20:51:46 UTC
I clicked the combined view and realized how to filter correctly... Had to play with it for a while, to realize that it is a correct behaviour. Sorry for this invalid bug.