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.
NetBeans IDE Dev (Build 200701311900) 1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105 Windows XP version 5.1 running on x86 Profiler 070202 I reproduced it everytime by these steps to reproduce: 1. start AnagramGame sample project outside ide using jdk 1.6.0 2. dynamically attach to the application, use CPU profiling all classes, entire application Result: instrumentation of the application is started but after a while ide throws an error the profiled application is not responding. The application is running and it takes 100% of system resources. I had to "solve" the problem by hard restart of machine.
Created attachment 37978 [details] profiled application's threadsdump
I am sorry, it works fine for me. WIndows XP, JDK 1.6.0 b105. Latest profiler.
Strange, try to reproduce it twice. It seems it doesn't work when other dynamic profiling was running in the ide before.
profiler build 070206 NetBeans IDE Dev (Build 200702061900) 1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105 Windows XP version 5.1 running on x86 new insllation 1. start AnagramGame sample project outside ide using jdk 1.6.0 2. dynamically attach to the application, use CPU profiling all classes, entire application Instrumentation done, but application frozen after it
I have nothing to add. The reproduction is clear for me and the problem is 100% reproducible. INCOMPLETE means reporter did not provide all information needed to reproduce the issue. I guess I cannot provide more now :).
The important thing making the difference is starting external application from .jar file, not from compiled .class files. For .class files dynamic attach works fine, for .jar the described problem occurs.
and that is not all! You need to run it with java -jar anagrams.jar other variants like java -jar .\anagrams.jar or java -jar dist\anagrams.jar work OK. Next time please specify your steps in more details. This will save us a lot of time. Many thanks to Jirka for discovering correct reproducible steps.
You should ask next time what dou you need to know. I can provide many other information like my uncle's name etc. :) The truth is it doesn't work for me with java -jar dist\anagrams.jar, java -jar anagrams.jar, java -jar .\anagrams.jar nor java -jar <ABSOLUTE_PATH> command line. So my hypothesis was it can be generalized to "the behaviour does not depend on the command line format". BTW Sometimes (not very often) before the application is blocked there is a message in application's log: Exception in thread *** JFluid Monitor Thread ***
I tried the case with classes (java -cp build\classes com.toy.anagrams.ui.Anagrams) and it does not work too. I think the problem is that it occures always in second and another dynamic profiling not in the first run (as I mentioned).
You are right. In some cases I am not able to reproduce it even with java -jar anagrams.jar It is also not 100% reproducible on your machine -> lowering priority to P2. It looks like some kind of timing issue.
Hopefully fixed in trunk. Please verify.
Cannot reproduce, verified
Thanks!