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.
After working a while with NB, it happens that starting the project in debugger does not work anymore. In the debugger console, it says "Listening on <port>", but the 2nd line "User program running" does not show up. But the java.exe process is visible in the task manager. Then, clicking on the "X" in the toolbar results in "User program finished", but it still shows in the execution window. "Terminate process" there results in a stacktrace in the output window (see below). From that point on, debugging never works. You have to restart NetBeans! Using q-build 20041102. NetBeans runs in JDK 1.5.0, project platform is JDK 1.4.2_05. java.lang.ThreadDeath at java.lang.Thread.stop(Thread.java:698) at java.lang.ThreadGroup.stopOrSuspend(ThreadGroup.java:671) at java.lang.ThreadGroup.stop(ThreadGroup.java:584) at org.netbeans.core.execution.DefaultSysProcess.stop(DefaultSysProcess.java:54) at org.netbeans.core.execution.ProcessNodeItem$1.stop(ProcessNodeItem.java:41) at org.netbeans.core.execution.ProcessNodeItem$TerminateProcessAction.performAction(ProcessNodeItem.java:69) at org.openide.util.actions.NodeAction$3.run(NodeAction.java:440) at org.openide.util.actions.CallableSystemAction.doPerformAction(CallableSystemAction.java:116) at org.openide.util.actions.NodeAction$DelegateAction.actionPerformed(NodeAction.java:438) at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849) at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169) at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420) at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258) at javax.swing.AbstractButton.doClick(AbstractButton.java:302) at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1000) at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1041) at java.awt.Component.processMouseEvent(Component.java:5488) at javax.swing.JComponent.processMouseEvent(JComponent.java:3093) at java.awt.Component.processEvent(Component.java:5253) at java.awt.Container.processEvent(Container.java:1966) at java.awt.Component.dispatchEventImpl(Component.java:3955) at java.awt.Container.dispatchEventImpl(Container.java:2024) at java.awt.Component.dispatchEvent(Component.java:3803) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822) at java.awt.Container.dispatchEventImpl(Container.java:2010) at java.awt.Window.dispatchEventImpl(Window.java:1766) at java.awt.Component.dispatchEvent(Component.java:3803) at java.awt.EventQueue.dispatchEvent(EventQueue.java:463) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:234) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149) at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
Similar behavior as #51552.
*** This issue has been marked as a duplicate of 51552 ***
Are you sure it is duplicate? The issue 51552 says nothing about the fact, debugger does not run any more after the problem. Also take in account that in the report user finishes session and then kils the process in runtime.
I'd like to add, that this has to be fixed in 4.0, not 4.1, as it is set as target in issue #51552. This is a major problem in a core component. And it will scare away (even more) users from NetBeans. I'll try to do further tests. What I already know is, that attaching to a remote JVM seems to be no problem. This problem only occurs for running the program from inside NetBeans. Maybe NetBeans tries to attach too early or something.
Is it 100% reproducible on your machine? Does it really block further usage of debugger in the session. Usually when it happens to me and I explicitly finish the non-started session by "Finish Session" I can run debugger again without problems. That's why I set my issue as P2. Please check also output tab of running application if you find there something and also do thread dump and attach it. Thanks. I will attach details to my issue #51552 since it's not clear it's really duplicate.
Debugger may not work at all or may work all the time. It is a threading issue with symptoms very close to Issue #51552. Different VMs behave differently in this case. Closing as duplicate. *** This issue has been marked as a duplicate of 51552 ***
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.