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.
Profiler 070314 NetBeans IDE Dev (Build 200703141900) 1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105 Windows XP version 5.1 running on x86 ru_RU (nb); Cp1251 Steps to reproduce: - Insert some profiling point - Start Profiling - Make sure the profiling point was hit - Modify it (for example, move to another place) - RESULT: Even it is shown in new place and links from reports show it in this new place correctly, the actual point that continues to be hit is the old one (prior to modification). This is confusing.
Moreover, if user disables some of them or even delete they continue to work. And in the latter case report will not be available.
You're right that Profiling Points are not modified on-the-fly, they should not be modified in any way during profiling. Disabling all Profiling Points actions during profiling will fix described problems. Ability to change Profiling Points in runtime the same way as breakpoints is a feature for future, will create new RFE for it.
*** Issue 97979 has been marked as a duplicate of this issue. ***
Disabled adding/modifying/deleting Profiling Points during profiling. This fixes problems described in this issue. Fixed for M9.
Created a RFE for modifying Profiling Points during profiling session: Issue 99260.
Verified with Profiler 070504 NetBeans IDE Dev (Build 070507) 1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105 Windows XP version 5.1 running on x86 ru_RU (nb); Cp1251