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.
Created attachment 144200 [details] Excerpt from IDE log. When you call "Stop Profiling Classes bellow this Line" action during memory profiling it kills GlassFish server. To reproduce: - create Java Web Application (JavaEE 7, GlassFish 4.0 server) - Invoke Profile -> Profile Project. Select Memory -> Analyze Memory -> Advanced, select both Record full object lifecycle, Record Stack Trace for Allocations. - Confirm dialog by Run button. - Press Live Results button and wait until the application is started. - Right-click char[] and choose Stop Profiling this Class. The class should disappear. - Sort classes by names (press header button of results table) and select e.g. the first class its name begins with org. Invoke action Stop Profiling Classes bellow this Line. - after while it becomes unresponsive and dialog with "Target JVM inactive" message appears Product Version: NetBeans IDE Dev (Build 201401200001) Java: 1.8.0-ea; Java HotSpot(TM) 64-Bit Server VM 25.0-b65 Runtime: Java(TM) SE Runtime Environment 1.8.0-ea-b123 System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb)
Can you please attach the log from the glass fish server?
Created attachment 144828 [details] Server log.
Created attachment 144829 [details] Java crash log.
According to java crash log, this looks like JDK issue.
I cannot reproduce it with JDK7u51: Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)
Created attachment 144898 [details] Java crash log with symbols
https://bugs.openjdk.java.net/browse/JDK-8035150
*** Bug 243562 has been marked as a duplicate of this bug. ***
*** Bug 246851 has been marked as a duplicate of this bug. ***