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 203103 - "Black Hole" when profiling NetBeans with jVisualVM
Summary: "Black Hole" when profiling NetBeans with jVisualVM
Status: RESOLVED INVALID
Alias: None
Product: profiler
Classification: Unclassified
Component: Ide (show other bugs)
Version: 7.0.1
Hardware: All All
: P3 normal (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-04 22:56 UTC by ceklock
Modified: 2011-10-05 17:23 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
jvisualvm about (30.12 KB, image/png)
2011-10-04 23:03 UTC, ceklock 		Details
jVisualVM before starting profile (52.95 KB, image/png)
2011-10-04 23:09 UTC, ceklock 		Details
jVisualVM running (58.76 KB, image/png)
2011-10-04 23:11 UTC, ceklock 		Details
jVisualVM running (2) (127.78 KB, image/png)
2011-10-04 23:14 UTC, ceklock 		Details
The "Black Hole" (36.29 KB, image/png)
2011-10-04 23:15 UTC, ceklock 		Details
jVisualVM running (3) (111.22 KB, image/png)
2011-10-04 23:33 UTC, ceklock 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ceklock 2011-10-04 22:56:59 UTC 
Don't know if this is a NetBeans issue, but when I am using jVisualVM and try to do a CPU profile of NetBeans (7.0.1 or 7.1 Beta) a "black hole" happens: NetBeans freezes and I can't close the window, can't do anything, the NetBeans window becomes black if I minimize and restore it.


Product Version = NetBeans IDE 7.0.1 (Build 201107282000)
Operating System = Windows 7 version 6.1 running on x86
Java; VM; Vendor = 1.6.0_27
Runtime = Java HotSpot(TM) Server VM 20.2-b06
Comment 1 ceklock 2011-10-04 23:03:52 UTC 
Created attachment 111489 [details]
jvisualvm about
Comment 2 ceklock 2011-10-04 23:09:47 UTC 
Created attachment 111490 [details]
jVisualVM before starting profile
Comment 3 ceklock 2011-10-04 23:11:40 UTC 
Created attachment 111491 [details]
jVisualVM running
Comment 4 ceklock 2011-10-04 23:14:24 UTC 
Created attachment 111492 [details]
jVisualVM running (2)
Comment 5 ceklock 2011-10-04 23:15:04 UTC 
Created attachment 111493 [details]
The "Black Hole"
Comment 6 ceklock 2011-10-04 23:17:25 UTC 
Maybe I just have to wait for the profiling to finish, but the strange part is that I cant close NetBeans. I have to go to the Task Manager to kill the process.
Comment 7 ceklock 2011-10-04 23:33:09 UTC 
Created attachment 111494 [details]
jVisualVM running (3)
Comment 8 ceklock 2011-10-04 23:34:15 UTC 
I think is not really a bug... Just have to wait for profiler to run. It took a long while for NetBeans to return to normality, but it returned.
Comment 9 Jiri Sedlacek 2011-10-05 09:35:51 UTC 
From the screenshots it's clear that you're trying to profile all classes in the NetBeans JVM incl. JDK classes. This imposes an extreme overhead causing the described problems - the application is unable to repaint its UI and doesn't respond to events like clicking the close button.

The suggested way of profiling large applications is to identify the possible bottleneck using Sampler and then use Profiler configured to profile just several classes. See these articles for more details on configuring the Profiler:

 - http://blogs.oracle.com/nbprofiler/entry/profiling_with_visualvm_part_1
 - http://blogs.oracle.com/nbprofiler/entry/profiling_with_visualvm_part_2

Closing as invalid, not a bug.
Comment 10 Tomas Hurka 2011-10-05 10:48:07 UTC 
Note that the problem with repainting is caused by instrumenting of all classes. Once the classes are instrumented, NetBeans will start repainting itself.
Comment 11 ceklock 2011-10-05 17:23:09 UTC 
Ok, thanks.