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 200706130000) Java: 1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105 System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb) org.netbeans.modules.profiler/1 [1.1.1 070612] I've noticed that there are many situations when "Profiled application doesn't respond" message appears. Typical scenario is as following: - Profiler has been attached to an application -or- Modify Profiling has been performed. - "Profiled application doesn't respond" message is shown after a while asking user whether to stop profiling. - Right after user presses "No", profiling starts. This behavior gives an impression that profiling is not possible until the dialog is shown and user selects No. The same time I believe that many users answer Yes to this dialog and do not receive any data. It would be nice if this dialog was not stopping the profiler and it was automatically dismissed once new profiling data was obtained.
Another situation: - I modified instrumentation of NetBeans profiling - There were lines about redefining xxx out of >2000 classes in the profiled NetBeans output. - When approximately 1800 classes out of >2000 were modified Profiler showed "Profiled application doesn't respond" message. - This message is disappointing in case user can't see that classes are being redefined at the moment
Product Version = NetBeans IDE Dev (Build 200708080000)
I believe this could be considered as P3 "Highly visible usability problem".
Fixed in trunk.
It was closed as fixed by mistake.
Failed to verify with Product Version: NetBeans IDE Dev (Build 200709271200) Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b05 System: SunOS version 5.10 running on x86; ISO646-US; en (nb) Profiled Application doesn't respond dialog is still shown.
Created attachment 49743 [details] Screenshot
Please provide steps how to reproduce it. It works for me.
The same steps as in the second comment. Used Profiler to profile second instance of NetBeans. Then slightly modified profiling. Profiled application doesn't respond appeared during classes redefinition.
You are right, the fix is not complete. :-(
Additional fix commited to trunk. Checking in src/org/netbeans/lib/profiler/ProfilerClient.java; /cvs/profiler/libs/jfluid/src/org/netbeans/lib/profiler/ProfilerClient.java,v <-- ProfilerClient.java new revision: 1.2; previous revision: 1.1 done Checking in src/org/netbeans/lib/profiler/server/ProfilerServer.java; /cvs/profiler/libs/jfluid/src/org/netbeans/lib/profiler/server/ProfilerServer.java,v <-- ProfilerServer.java new revision: 1.2; previous revision: 1.1 done Checking in src/org/netbeans/lib/profiler/wireprotocol/WireIO.java; /cvs/profiler/libs/jfluid/src/org/netbeans/lib/profiler/wireprotocol/WireIO.java,v <-- WireIO.java new revision: 1.2; previous revision: 1.1 done
Verified with Product Version: NetBeans IDE Dev (Build 200710301200) Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b06 System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb)
See also issue 120639