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 146609 [details] log This is what happens: 1. I double click the netbeans icon 2. Splash screen appears 3. Splash screen gets until "Done loading modules." 4. Splash screen disappears 5. netbeans63.exe process just hangs there with 0 CPU load and around 320 MB Ram 6. NO UI shows up - nothing happens any more Killing the process and restarting doesn't help. No errors in the log as far as I can see. messages.log is attached. This is the third time this happens and I'm fed up with re-installing Netbeans and/or setting up my netbeans profile from scratch. So please don't tell me that my installation is broken and that I need to re-install. Instead please tell me what fucked up my installation so I can avoid it in the future. Thanks.
BTW, re-installing alone does not help. The only thing that seems to be helping is deleting the folder %USERPROFILE%\AppData\Roaming\NetBeans\8.0 and re-configure everything from scratch.
*** Bug 243428 has been marked as a duplicate of this bug. ***
I don't think it's the launcher issue. The log ends after loading modules and proxy resolving... Reassigning to Module system. Jarda, please look at it.
Can you attach thread dump of the process?
(In reply to Jaroslav Tulach from comment #4) > Can you attach thread dump of the process? I'm not sure how to reproduce the problem. It hasn't happened for the last few days now. Maybe it was a bad plugin or something? If it happens again I'll try to create a dump. I assume I could use something like ProcDump for that? http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx
Just happened again. This time on Mac OS X. Don't know how to do a thread dump or whatever you need. I'll list what happened before: 1. JBoss App Server plugin fucked up - didn't actually stop the server although server was marked as stopped in Netbeans 2. I started a new debug session which tried to start JBoss server again but that lead to "Address already in use" exception. 3. I tried to stop the Debug process --> no reaction in Netbeans 4. Quit Netbeans --> Window popped up "Running processes: Do you really want to exit?" or something like that. 5. Clicked "Exit" Now Netbeans doesn't start anymore... :(
Created attachment 146795 [details] Java Thread Dump Thread dump
NbMavenProjectFactory.loadProject tries to query lookup and that goes to org.zeroturnaround.jrebel.netbeans.navpanel.JRebelNavTopComponent.<init> which then tries to access AWT lock. Meanwhile AWT is testing enabled state of MainProjectAction and blocks on project mutex: SimpleFileOwnerQueryImplementation.getOwner
if there will be safe fix delivered in reasonable time frame, we can put it into patch1
awt components should not be constructed in off-AWT threads, jrebel integration has to cater to that.. Not much that can be done on the maven or generic project side. wontfix, please file against the jrebel plugin (no idea where exactly that is)
I was very surprised that NetBeans sometime starts create TopComponent in non AWT Queue, I have added fix for that and since NB plugin 5.5.3 it will be fixed