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.
I have started recently using Netbeans with Java 6 Update 14. When running the debugger on my project, and when one of the breakpoints is hit, the continue button does not become enabled. In addition, the keyboard shortcut for Continue: F5 does not work either. Switching back to Java 6 Update 13 fixes this issue.
Vojto(vsigler), could you please confirm : this is JDK6u14 regression? We are going to bundle NB 6.7 with JDK6u14 so if there is more problems like this, we need to know about them ASAP. Thanks in advance.
I've tested 6.5.1 and 6.7 RC2 (Build 200906042131) on both WinXP and Linux, but I was unable to reproduce this issue. Plus I've been testing RC2 using JDK 1.6u14 most of this week without any problems. @grimlock81: Could you please provide more info on this issue? Some more exact steps to reproduce would be also very appreciated (type of breakpoint, maybe sample code, etc.). Does the debugger console show something unusual when this occurs, does it display "breakpoint hit"? Are there any error messages in messages.log?
Well, there was issue #160747, which was recently fixed. That issue was reported for 6.7 dev builds, but perhaps there was some problem in 6.5 as well... This was a random issue, thus it can happen that it's disabled only sometimes. grimlock81, do you have Continue consistently disabled on JDK 6 up 14? Can you try that please in NetBeans 6.7 RC?
I remember coming across this issue when using some of the Early Access builds of Update 14 a month or so ago. I put it down to using a pre-release and happily went back to Update 13. I installed the actual release Update 14 yesterday and encountered this problem again. Unfortunately the code is on my work computer, and it is a long weekend here so I can only give you an update in 3 days time. I'll try to create the same issue on my home computer. Some other information: - The project running in the debugger is a Swing application. - I had another class from the same project running in Netbeans, but not in the debugger. - After I switched back Update 13, the Continue button was enabled at breakpoints again. - Netbeans 6.5 but with the latest updates from the Update Center installed.
No error messages in messages.log "Breakpoint hit at line XXX in class XXXX by thread XXXXX" is printed in the console when the breakpoint is hit. There are breakpoints that do allow the Continue button to be enabled and also others that do not allow the Continue Button to be enabled. All breakpoints that occur on the Event Dispatching Thread do not allow the Continue button to become enabled. Breakpoints on other threads besides the EDT may or may not allow the Continue button to become enabled. I have encountered the problem on two separate projects of mine. I have tried but failed to reproduce a simple test case that replicated this error.
Problem does not occur in Netbeans 6.7 RC2
Spoke too soon. I've just had it happen in 6.7 RC2. The interesting thing is it happened after I copied the netbeans.conf file from 6.5 into 6.7 RC2 and I'm guessing the value of netbeans_default_userdir being set to ${HOME}/.netbeans/6.5 is responsible. Perhaps some value in one of the files under ${HOME}/.netbeans/6.5 is causing the issue. Any particular file(s) I should be on the lookout for?
@grimlock81: Thank you very much for your input. It could a problem with imported settings from 6.5. Could you, please, try working with your projects with a clean userdir (no importing from 6.5)? You can do it by running netbeans with a command line parameter --userdir /path/to/new/userdir. I'll do some more tests of my own in the meantime. Thanks a lot!
I tested it again under both WinXP and Linux, also with importing userdir from 6.5.1 to 6.7 but with no success. I also tried placing breakpoints in the Event dispatching thread, but every time a breakpoint was hit, the continue button was enabled and the action worked. Does the problem persist when using a clean userdir? Thanks
There's a hypothesis that http://bugs.sun.com/view_bug.do?bug_id=6862295 is causing this - since there's a regression with threads ID change on Windows, it can possibly confuse the logic that determines if all threads are running/suspended and therefore not enable correctly Pause/Continue. It should be tested again after http://bugs.sun.com/view_bug.do?bug_id=6862295 is fixed.
grimlock81, since you can reproduce this problem, can you please test if adding this option: -XX:+UseParallelGC into etc/netbeans.conf (to netbeans_default_options) will solve the problem on JDK 6u14? Thanks.
Okay, I've added the option to the netbeans.conf file. I'll post an update in a few days time.
Note you need to use the -J prefix in netbeans.conf file, so it should be -J-XX:+UseParallelGC
*** Issue 169617 has been marked as a duplicate of this issue. ***
I can confirm this issue on NB6.7.1 jdk6u14 upgraded from NB5.5=>6=>7 ...
workaround: hit pause, hit continue
I added the flag -J-XX:+UseParallelGC to netbeans_default_options for my netbeans.conf file. I still encountered this issue.
As mentioned in issue #167776, this problem is caused by thread ID changes. We implement a workaround in NetBeans till it's fixed in JDK. Besides this there's also an occasional inconsistency in NetBeans debugger, which also caused disabled Continue regardless on JDK version. This will be resolved in issue #167776.
Workaround for JDK bug implemented in changeset: 140591:8e4ac65c2f8a http://hg.netbeans.org/main/rev/8e4ac65c2f8a
Integrated into 'main-golden', will be available in build *200908080201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/8e4ac65c2f8a User: mentlicher@netbeans.org Log: #166579 - Synchronize the cached threads with VM threads when we get an event in a thread that is not cached. This is a workaround for http://bugs.sun.com/view_bug.do?bug_id=6862295.
Created attachment 86179 [details] messages.log
Created attachment 86180 [details] This is the stack trace for AWT-EventQueue-1 when viewed under JConsole
Installed Java 6 Update 16 and it seems to have fixed this problem. However, I'm starting to get complete freezes of the whole IDE. This occurred in Update 15 as well
grimlock81, this freeze is a duplicate of the issue #168613. It's a bug of NetBeans :-(, so it occurs on all JDK versions. It's fixed already in 6.8 dev builds and I hope it will be provided as a patch to 6.7 (or 6.7.1).
*** Issue 171689 has been marked as a duplicate of this issue. ***
*** Issue 171769 has been marked as a duplicate of this issue. ***
v/c