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 1.2 070703 Product Version: NetBeans IDE Dev (Build 200707031200) 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) Got a freeze of profiler application and IDE performing the following steps: - Created New Anagram Game Project - Inserted two Profiling Points: Stopwatch on first line of nextTrialActionPerformed method and Load Generator on first line of guessedWordActionPerformed (specified html file for the script) - Started CPU Profiling with default options - Played with application, pressed Guess button several times repeatedly - RESULT: Both profiled application and IDE became frozen. After some timeout "profiled application do not respond" dialog was shown and IDE became responding. However, it got frozen again each time this dialog was canceled. Only after it was confirmed IDE became to normal state while the profiled application still left non-responding and had to be killed.
Created attachment 44770 [details] Application thread dump
Created attachment 44771 [details] NB thread dump
Created attachment 44772 [details] Application thread dump 2nd run
Created attachment 44773 [details] NB thread dump 2nd run
Profiling is not able to start after this freeze, IDE should be restarted.
Created attachment 44774 [details] Output on attempt to profile application after freeze
When user tries to start profiling after freeze, there is a "starting profiling session" process shown in the status bar which continues to run after profiler failed to start and after Stop Profiler button is invoked in Profiler Control Panel. Profiler state is shown as Started in it.
Created attachment 44775 [details] Nb thread dump while Start Profiling Session process is run
Created attachment 44813 [details] Application thread dump 3rd
Created attachment 44814 [details] NB thread dump 3rd
This was caused by the fact that a plain HTML file was selected as a JMeter script specification. The JMeter engine then failed and the PP caused unpredictable behavior. Now this is properly fixed and a wrong script file or any other exception thrown within a loadgenerator engine is handled. Also it's impossible to specify a script file that is not supported by a registered loadgenerator engine (the check is done by the file extension for now)
Verified with Product Version: NetBeans IDE Dev (Build 200708211200) 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)