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.
Hello, I'm referencing to my enrty in the mailing list. See a copy at the end of this text. In the meantime I've upgraded to NB 6.1 ( from NB 6.1 RC2 ). Now the behavior differs a bit. The button "Reset Collected Results Buffer" now works. But when I click to "Modify Profiling Session..." the following happens: 1. Message: "The profiled application does not respond. " 2. Action: I click "Yes" to stop the profiled application. 3. Message: "Stopping profiled server failed" Next I closed the IDE and still one JAVA Process keeps alive. I'll attach the IDE-log to this issue. I couldn't produce a thread dump, as suggested, because I running JDK 5 and not JDK 6, which is reported to be necessary to get the thread dump with VisualVM. B.t.w, I'm trying to profil an 'ear' application containing MDBs. Further I'm using the genericra in conjunction with the client jars from IBM MQ series. Trying to get a stable and repeatable Memory Profiling I'm running from one issue to an other. So it's difficult to report such a bug. Best regards Andreas Hi Andreas, could you please file a bug report for the profiler at http://www.netbeans.org/issues/enter_bug.cgi?component=profiler and attach the IDE logfile there? Also, if the IDE seem to be hanging please take thread dumps of both the IDE and profiled application (you can use VisualVM tool to take simultaneous thread dumps from two apps). It will help us to find out the problem. Thanks, Jiri Simon, Andreas wrote: > Hello, > > the problem occurs when clicking the button "Reset Collected Results > Buffer". The IDE hangs and when closing the IDE, one JAVA process > keeps alive. I've to kill it with the TaskManager ( Win NT, SP2, JDK > 1.5, 15 ). > > The backtrace option was disabled. > > Regards > Andreas >
Created attachment 61036 [details] IDE logs to issue 134504
Hi, I try to reproduce the failure with the following environment: NB 6.1, java version "1.6.0_06" instead 1.5.0_15. Now the described scenario seems to work. That's the goog news. Now the an error occurs in memory profiling when clicking "Stop profiling classes below this line". But this error doesn't not disturb me in my tests. So I would suggest to close this issue. Regards Andreas
Closed based on reporter's feedback.
VERIFIED in build 200901120201