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 160044 [details] Thread dump of the debugged ide. I can reproduce this issue on my machine currently always. I have one ide that is build from hg repository today. The second ide is daily Java SE build from 20160614. I'm trying to attach the java debugger from the daily build ide (used as develper ide) to the debugged ide (build from trunk). The attaching is finished correctly, you can start and stop threads in the debugging window. But the debugged ide is not responsive, because the AWT thread is waiting for a lock and it looks like AWT-XAWT thread is still running (consume 100% of one processor). The thread dump of the debugged ide is attached. When you finish the debug session, then the debugged ide works correctly. If I connect a debug session to the same debugged ide from NB 8.1, then it works correctly. If I try to connect session from the mentioned daily build, then doesn't work again.
Adding Mila to the cc, if the problem is in the editor.
The debugged ide I run with these options: netbeans -J-Dkenai.com.url=https://testkenai.com -J-XX:+HeapDumpOnOutOfMemoryError -J-Dnetbeans.debug.exceptions=1 -J-Dorg.openide.util.NbBundle.DEBUG=false -J-Dnetbeans.hack.50423=true -J-Xdebug -J-Xnoagent -J-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8002 --jdkhome /home/petr/jdk/jdk1.8.0_31 --userdir /home/petr/ide/userdir/jsdebug10 -J-Dorg.netbeans.modules.javascript2.editor.JsCodeCompletion.level=FINEST -J-Dorg.netbeans.modules.javascript2.editor.parser.SanitizingParser.level=FINE -J-Dorg.netbeans.modules.javascript2.editor.parser.JsParser.level=FINE and the dev ide i run with these: netbeans -J-Dsun.java2d.pmoffscreen=false --jdkhome /home/petr/jdk/jdk1.8.0_31 --userdir /home/petr/ide/userdir/javascript-trunk
For me the debugger is very slow in dev build. Attach takes ~ 3min. Step over statement i+=2 takes ~ 1min.
observed the same - attach is slow - stepping is slow - the whole debugged application becomes very slow
Thanks to Mila's logs it seems that the performance problem is caused by this method breakpoint created by JSJavaBreakpointsManager: MethodBreakpoint inNashorn = MethodBreakpoint.create("jdk.nashorn.*", "*")
Finally reproduced after attaching debugger to another NetBeans instance that have opened and rebuilt JavaFX project.
Fixed by changeset: 300823:6f4091c5ad8d http://hg.netbeans.org/core-main/rev/6f4091c5ad8d Please verify.
I confirm that the fix eliminates the problem: the debugger attaches quickly to the debugged application and the application does not freeze. Thanks for fixing.
Thanks for the prompt verification, the fix is pushed into release82 branch: http://hg.netbeans.org/releases/rev/51a2c1fbfc1f
Integrated into 'main-silver', will be available in build *201609220002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/6f4091c5ad8d User: mentlicher@netbeans.org Log: #262424: Do not use method breakpoints that spans accross too many classes.