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.
[ BUILD # : Dev 20050318 ] [ JDK VERSION : 1.5.0_02 ] In a Swing application, when you call setDefaultLookAndFeelDecorated(true), the application never appears when run in the debugger. This is mostly repeatable, but every once in awhile it will start to debug correctly until recompiled. Include the call in the main() method: public static void main(String args[]) { java.awt.EventQueue.invokeLater(new Runnable() { public void run() { JFrame.setDefaultLookAndFeelDecorated(true); new SwingTest().setVisible(true); } }); } Compile and run the application in the debugger. The IDE will switch to debugger mode. The "Debugger Console" tab in the Output window will display nothing. The "<Project Name> (debug)" tab in the Output window will display: init: deps-jar: compile: The application debugger state will show as running, and the Runtime window will show a "<Project Name> (debug)" process running. However, the application main window will never be displayed, and any breakpoint set will not be triggered. When you stop the application (Ctrl-F5), the debugger session will end, but the debug process will still be shown as active in the Runtime window. the process must be terminated to end it. When you comment out the setDefaultLookAndFeelDecorated(true) call, the application runs and stops in the debugger correctly.
Created attachment 20967 [details] Example Swing application.
I managed to reproduce that as well. It doesn't seem to be related to setDefaultLookAndFeelDecorated(true) call. Please attach thread dump (Ctrl+Break on Win) taken when it happens. Increasing priority to P2. It's not reproducible everytime but frequently.
Created attachment 20981 [details] thread dump
Please evaluate the issue, it would be P1 when it's reproducible reliably.
I have an evidence it is not related to swing applications. I reproduced the issue (Win XP, NB build 200503170655 on jdk 1.5.0_02) with simple console application which only writes strings into console. The same behaviour can be seen when starting debugger via Step Into or Run to Cursor actions.
*** Issue 56536 has been marked as a duplicate of this issue. ***
Created attachment 20982 [details] Thread from unsuccessful debugger start of console application
*** Issue 56657 has been marked as a duplicate of this issue. ***
Created attachment 20997 [details] Output from verbose debugger start
We are facing this bug when trying to start web module on App server or Tomcat server in debug mode. It happens quite rarely for me (but sometimes several times in a row). The Deploy task works well but JPDAConnect doesn't success because of synchronization problems. I run NB with -J-Dnetbeans.debugger.start option and I put some additional 'printlns' into JPDADebugger.attach() and JPDADebuggerImpl.waitRunning() methods. The typical case is that thread in which nbjpdaconnect task is run is suspended on the LOCK2 object (in JDAPDebuggerImpl.waitRunning() ) and never resumed. Attaching a thread dump and a relevant part of message.log.
Created attachment 20998 [details] message.log when 'debug project' action executed twice
Created attachment 20999 [details] Thread dump obtained immediatelly after connect task freeze
Fixed in TRUNK.
rondurska: please always set target milestone correctly when you close the bug, in this case to "4.1". Thx
Doesn't work with build 200503232205 on Win XP Pro. Attaching two thread dumps.
Created attachment 21086 [details] Taken while debugger waits at a breakpoint.
Created attachment 21087 [details] Taken after Continue. Swing app now frozen.
I think you are now facing issue #56863. If debugger is sucesfully started, do not reopen this issue, this issue is solely about debugger start.
Closing (see above).
Verified in nbdev 200507061800.
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.