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 decided to retsrat Netbeans after encountering a problem in the design screen - (my created design was not displaying). When I tried to restart netbeans, it hanged. I rebotted my computer, and it hanged on startup yet again - sometime after it had finished loading modules. I uninstalled Netbeans 5 and installed it again, and I got the same problem. I rebotted, and the problem still persists. I cannot get NB to do anything - it hangs in startup always when it says: 'done loading modules'.
Please first check if it hangs in startup script or in JVM: When it hangs check if there is java process connected to your console. If yes get thread dump and attach it here. If it hangs in startup script add set -x to 'netbeans' and 'nbexec' shell scripts. It will output verbose log to console. Reassigning to core. Please also add info what OS, JDK, NB build you use.
I am seeing the same problem on Windows XP Pro with (first) the 9/16 build, and now the 9/19 build. In both cases: * installed the build * started NB * visited the update center & downloaded some of the offerings * restarted * spent time working on an applet UI * stopped NB * started NB (the next day) ... or tried to as it hung (no CPU or notable disk activity) after declaring that it was done loading modules. There is nothing obviously unusual in the message.log. Not clear for want you are asking, but will try running the netbeans.exe with -x to see if this produces something useful.
Ah - forgot to add this was with JDK 1.5.0_05. After killing the hung NB process, started from command line with "bin\netbeans -x" ... and it worked (successful startup). Stopped and started from the command line w/o "-x" ... and it worked. Stopped and started from the installed Windows desktop ... and it worked. FWIW - the hung process had 16 seconds CPU used. After NB starts successfully, the CPU use totals 24 seconds. Perhaps there is something causing trouble run by NB only once(?) per day?? Will attach the message.log, but nothing of obvious interest.
Created attachment 25077 [details] Log with both successful and hung startups (not evident from log)
Following the theory that the hang may be related to something done by NetBeans once a day on startup... Today's test was slightly different. NetBeans was left running overnite. Shutdown the running instance of NetBeans. Started a new instance of NetBeans (or tried to). The new instance hung on startup exactly as described before - after NB announces it is done loading modules (and after 16 seconds total CPU used) ... nothing. After a few minutes (long enough to upgrade Firefox to 1.0.7, bring up this page and enter the above) killed the hung NB instance. Tried starting NB again, and it started up successfully.
Created attachment 25117 [details] Today's messages.log file. Nothing of obvious interest. Is there a way to get a more detailed/interesting log?
Please get thread dump as I suggested above to find out if it is deadlock or something else. On Linux press Ctrl-\ from console. On Windows you must run nb.exe from console and press Ctrl-Pause I think from console. You get thread dump. Copy/paste it to file and attach here.
FYI- Have not seen another occurance after upgrading to the NetBeans 5.0 beta.
jenikya, thanks for help. Closing worksforme
Apparently this behavior just went into hiding(?). Started NB 5.0 beta this morning after a reboot, and got the same symptoms (17 seconds CPU used). Since I was not expecting trouble, did not start from the command line (thus no thread dump).
Created attachment 26076 [details] Log with both successful and hung startups (not evident from log)
There may be a clue in the log. The hang was in "Turning on modules:" between the two items: org.netbeans.modules.websvc.dev/1 [1.3.1.1 200509261930] org.netbeans.modules.web.examples/1 [1.3.1 200509261930] In the hung-startup the first of the above two is listed, but not the second.
For JDK 6.0 there is utility jstack also for Windows. First use jps to find out PID of your java process and then use jstack to get thread dump. Run both from console. Of course you should run IDE also on JDK 6.0. You can download EA binary build of JDK 6.0 from https://mustang.dev.java.net/ ie. no need to run IDE from console.
pbannister, we need the thread-dump of locked IDE. Without this information we are not able to do anything. So please follow the steps mslama wrote above, or look at the page: http://qa.netbeans.org/bugzilla/generating-thread-dumps.html I am closing this as worksforme. If you got the same problem once again, generate the thread-dump and reopen this issue. Thanks in advance.