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.
Steps to reproduce: 1. I choose Run Main Project from the Run menu, which then causes Tomcat to start. 2. Profile->Attach and Profile 3. I click the big Analyze Performance button on the big profile dialog box. 4. I click the Part of Application radio button 5. I click the Select... button to choose a root method. 6. After selecting the method I highlight it in the list that is in the Specify Root Methods dialog. 7. I click on the attach button of the big profile dialog box and then put in the PID for Tomcat and click OK. 8. The profiler attachs to Tomcat and I see the standard three graphs, but on the bottom border of the NetBeans window it says: Instrumentation - None. This is a bit confusing to me. I selected "Analyze Performance," so why am I not analyzing CPU performance? 9. I Exercise the application so that it will hit the selected method. Bottom border of the NB window now says: Instrumentation: CPU, 5 methods instrumented. 10. Click the Get Current Results icon and the message "No profiling results available yet" is displayed. This seems a bit odd. 11. Click "Modify Profiling" 12. Click Select... button to choose a root method. The Specify Root Methods dialog displays and the method I selected is still shown in the list box, but it is no longer highlighted. 13. So I highlight the method in the list that is in the Specify Root Methods dialog. 14. Click OK. 15. Exercise the app. to again hit the selected method. Bottom line of window now says: Instrumentation: CPU, 3419 methods instrumented 16. Click the Get Current Results icon and see the CPU performance numbers.
Fixed in Milestone 5 release. What worries me is that this seemed like a real regression (i.e. it was not specific to Web apps or something, the problem would be the same for any application we dynamically attach to, that doesn't have the root method's class loaded yet), and it went unnoticed, probably for quite some time.
Verification of old issues.
Closing old issues.
Reverting to the original Target Milestone value changed by mistake. Sorry for inconvenience.