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.
Product Version: NetBeans IDE 6.0 RC1 (Build 200711090000) Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05 System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb) Steps to reproduce: - Start CPU profiling of Anagram Game Application: Entire Application, Profile all classes - Open Live Results and DrillDown - Select com.toy.anagrams.lib.WordLibrary.getScrambledWord(int) - Disable Auto-Update - Play with application until method categories are updated. I also got an update when no method was selected (see attached screenshot).
Created attachment 52784 [details] Screenshot
The DrillDown is a separate component - it doesn't know about the enablement of auto update. Will have to address it in a post 6.0 release
I'm not sure if we want to change the current behavior. Mrkam, could you please explain why this is a bug? DrillDown is a separate view/TopComponent, it has no "Disable Update" button. Moreover there is no UI relation between Live Results and DrillDown, the user doesn't expect that settings in Live Results will affect DrillDown. Currently DrillDown is pure live information, when profiling is finished, it's closed. I'm not sure if pausing DrillDown makes any sense at all.
Currently DrillDown is not updated while auto-update in Live Results is disabled. Probably I should file another issue about that, however from user's point of view there is a clear link between Live Results and DrillDown: - DrillDown is opened from Live Results and there is no explicit way to open DrillDown without Live Results by default (no menu item in Window menu, no button in profiler control panel) - DrillDown is attached to Live Results by default, and is shown only when Live Results are shown - When user selects method in Live Results, its category distribution is shown in DillDown - When user selects category in DrillDown, the filter is applied to Live Results So the current behavior (except of this issue) seems to be the most natural, doesn't it?
After re-evaluation it's obvious that not only the DrillDown component gets updated but the whole LiveResults panel. And the reason for this is the fact that the server buffers for profiling results are full and they get dumped to the client. And the client is bound to process them - doing so it will deliberately update the live results tables as well as the DrillDown component so they reflect the latest known state. The "Auto-Update" feature is merely telling the profiler to poll for data while in the case described here the data is pushed from the server and disabling "Auto-Update" works correctly. Closing this issue as invalid.