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 218262 - Profiler connecting forever
Summary: Profiler connecting forever
Status: VERIFIED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Ide (show other bugs)
Version: 7.3
Hardware: All All
: P1 normal with 1 vote (vote)
Assignee: Tomas Hurka
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2012-09-13 07:45 UTC by Jiri Skrivanek
Modified: 2014-05-01 16:18 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Jiri Skrivanek 2012-09-13 07:45:49 UTC 
Profiler doesn't work. It cannot connect to target VM. To reproduce:

- run IDE with empty userdir
- create new Java project
- wait until scanning finishes
- right-click project node and choose Profile
- click Run to start profiling
- Progress dialog appears with message "Connecting to the target VM..." and it is up forever
- it is the same if you try calibration

Product Version: NetBeans IDE Dev (Build 201209130001)
Java: 1.7.0_07; Java HotSpot(TM) 64-Bit Server VM 23.3-b01
System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb)
Comment 1 Jiri Sedlacek 2012-09-17 15:44:44 UTC 
Reproducible.
Comment 2 Jiri Sedlacek 2012-09-17 15:46:25 UTC 
Looks like a JDK bug. As a workaround please run the profiled application using JDK 6 or an older JDK 7 update.
Comment 3 Tomas Hurka 2012-09-17 15:58:24 UTC 
I was able to reproduce it on Linux too.
Comment 4 Tomas Hurka 2012-09-18 06:44:41 UTC 
This regression was caused by 113926b00f26 and it can be reproduced on JDK 7. JDK 6 works fine.
Comment 5 Tomas Hurka 2012-09-18 09:31:30 UTC 
Fixed in profiler-main

changeset:   233299:56fa534994ed
user:        Tomas Hurka <thurka@netbeans.org>
date:        Tue Sep 18 11:05:09 2012 +0200
summary:     bugfix #218262, assert logic in Monitors class is initialized too early and it collides with ProfilerRuntime.waitEntry()
Comment 6 Quality Engineering 2012-09-19 03:01:34 UTC 
Integrated into 'main-golden', will be available in build *201209190001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/56fa534994ed
User: Tomas Hurka <thurka@netbeans.org>
Log: bugfix #218262, assert logic in Monitors class is initialized too early and it collides with ProfilerRuntime.waitEntry()
Comment 7 Jiri Skrivanek 2012-09-19 10:31:14 UTC 
It works just first time. If you try to start profiling again, it shows just progress dialog as before.
Comment 8 Tomas Hurka 2012-09-19 11:00:41 UTC 
The original problem is fixed. We are not able to reproduce it on Linux and WIndows and we are able to profile several times in the row. If you still have a problem, please file a separate issue. Thanks.
Comment 9 Jiri Skrivanek 2012-09-19 12:14:29 UTC 
Bug 218611 filed for repeated profiling.
Comment 10 witbrock 2014-05-01 16:18:33 UTC 
This issue (or something remarkably like it) is still present in NB 8.0