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 Dev (Build 200708140000) Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b05 System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb) Steps for reproduce: Create new java libary project. Add new class NewClass extending JApplet base class. Select created class in Projects view and invoke Profile | Profile Other | Profile 'NewClass.java'. First time profiling dialog shows. Confirm it. Select Profiling Task dialog not shown after that. Need to invoke Profile Other command again.
Once the file is created but its source not opened, invoking Profile NewClass.java results in either SPT dialog opening or "Can not start profiler" message, approx 1:1. If the source is opened, SPT dialog is correctly shown only after source coloring has been finished => probably problem with lazy source processing leading to incorrect information obtained from Java infrastructure. I believe this is P2 since the user has no idea why the actions doesn't work sometimes and incorrect message is shown.
fixed in trunk this is not related to lazy action enablement evaluation - the core problem was that for a class to be told whether it's an instance of another class/interface the controller must be at least in "RESOLVED" phase - the "PARSED" phase is not enough
Verified in build 200709031200