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 95291 - Find in Hot Spots doesn't work if filter is enabled
Summary: Find in Hot Spots doesn't work if filter is enabled
Status: NEW
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Jiri Sedlacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-12 15:54 UTC by Alexander Kouznetsov
Modified: 2007-02-12 16:25 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
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 Alexander Kouznetsov 2007-02-12 15:54:07 UTC 
Profiler 070212
NetBeans IDE Dev (Build 200702111900)
1.5.0_10; Java HotSpot(TM) Client VM 1.5.0_10-b03
Windows XP version 5.1 running on x86
ru_RU (nb); Cp1251

Steps to reproduce:
- Open CPU snapshot 
- Activate filter in Hot Spots view
- Right-click some entry in Call Tree and select Find in Hot Spots
- RESULT: No entry is shown in Hot Spots if it is already filtered out.
Comment 1 Jiri Sedlacek 2007-02-12 16:02:35 UTC 
Similar problem occurs also for HeapWalker. What do you think is the best 
solution? We can either don't show the entry from Call Tree (current approach) 
or change current filter in Hot Spots to include the entry (the user may not 
notice it)? I'm not happy with any of these possibilities but I don't know 
about any better solution.
Comment 2 Alexander Kouznetsov 2007-02-12 16:25:17 UTC 
I feel that there is no best solution. Since user could easily restore filter I
believe it is okay to disable filtering if the item is filtered out. Modifying
filter is error-prone and could be misleading. Consider also applying filter to
Call Tree.