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.

Bug 240763 - "Stop Profiling Classes below this Line" stops GlassFish server
Summary: "Stop Profiling Classes below this Line" stops GlassFish server
Alias: None
Product: platform
Classification: Unclassified
Component: JDK Problems (show other bugs)
Version: 8.0
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Antonin Nebuzelsky
Keywords: JDK_8
: 243562 246851 (view as bug list)
Depends on:
Reported: 2014-01-21 12:37 UTC by Jiri Skrivanek
Modified: 2014-09-03 13:05 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Excerpt from IDE log. (2.30 KB, text/plain)
2014-01-21 12:37 UTC, Jiri Skrivanek
Server log. (111.11 KB, text/plain)
2014-02-05 12:57 UTC, Jiri Skrivanek
Java crash log. (38.07 KB, text/plain)
2014-02-05 12:57 UTC, Jiri Skrivanek
Java crash log with symbols (38.20 KB, text/plain)
2014-02-07 08:11 UTC, Tomas Hurka

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Skrivanek 2014-01-21 12:37:46 UTC
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)
Comment 1 Tomas Hurka 2014-02-05 12:07:53 UTC
Can you please attach the log from the glass fish server?
Comment 2 Jiri Skrivanek 2014-02-05 12:57:28 UTC
Created attachment 144828 [details]
Server log.
Comment 3 Jiri Skrivanek 2014-02-05 12:57:56 UTC
Created attachment 144829 [details]
Java crash log.
Comment 4 Tomas Hurka 2014-02-06 10:55:37 UTC
According to java crash log, this looks like JDK issue.
Comment 5 Jiri Skrivanek 2014-02-06 11:00:42 UTC
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)
Comment 6 Tomas Hurka 2014-02-07 08:11:42 UTC
Created attachment 144898 [details]
Java crash log with symbols
Comment 7 Antonin Nebuzelsky 2014-02-18 10:16:49 UTC
Comment 8 Tomas Hurka 2014-04-04 14:12:34 UTC
*** Bug 243562 has been marked as a duplicate of this bug. ***
Comment 9 Tomas Hurka 2014-09-03 13:05:46 UTC
*** Bug 246851 has been marked as a duplicate of this bug. ***