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.
Product Version: NetBeans IDE Dev (Build 201208310001) Java: 1.7.0_08-ea; Java HotSpot(TM) 64-Bit Server VM 23.4-b01 System: Mac OS X version 10.8 running on x86_64; US-ASCII; en_US (nb) User directory: /Users/tomas/Library/Application Support/NetBeans/dev Cache directory: /Users/tomas/Library/Caches/NetBeans/dev ------------------ I've seen this behaviour couple times recently.. - created new project (seems like project type does not matter, java, javaee,..) - go through the wizard, push Finish - wizards gets closed, but no project is opened in projects window - in this state, it's imposible to invoke new project wizard again, action does nothing. No exception in log, etc. Project itself seems to be created, it's possible to open it via Open project dialog.
hmm.. thread dump maybe? have you tried the menu/toobar/shortcut for the action once it "hangs"?
Created attachment 123775 [details] threaddump Fortunately I kept thread dump. Tried invoking from icon as well as menu. Did not try shortcut, but I expect it would be the same.
great, the problem seems to be outside of project support scope (see below), moving to platform for evaluation. "NewProjectBody" daemon prio=5 tid=0x00007fac28071000 nid=0x411f in Object.wait() [0x0000000160f86000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x000000012155d330> (a org.netbeans.core.windows.services.DialogDisplayerImpl$1AWTQuery) at java.lang.Object.wait(Object.java:503) at org.netbeans.core.windows.services.DialogDisplayerImpl.notify(DialogDisplayerImpl.java:291) - locked <0x000000012155d330> (a org.netbeans.core.windows.services.DialogDisplayerImpl$1AWTQuery) at org.netbeans.core.windows.services.DialogDisplayerImpl.notify(DialogDisplayerImpl.java:167) at org.openide.loaders.TemplateWizard.instantiateImpl(TemplateWizard.java:504) at org.openide.loaders.TemplateWizard.instantiate(TemplateWizard.java:392) at org.netbeans.modules.project.ui.actions.NewProject.doPerform(NewProject.java:135) at org.netbeans.modules.project.ui.actions.NewProject.access$000(NewProject.java:91) at org.netbeans.modules.project.ui.actions.NewProject$1.run(NewProject.java:101) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1454) at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2036)
I've added timeout to DialogDisplayerImpl.notify(). Hopefully it'll fix this problem and won't break anything else. core-main 8a54c267b926
It could be also related to AWT scheduling error(s) in Mac JDK too...
Integrated into 'main-golden', will be available in build *201209050001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/8a54c267b926 User: S. Aubrecht <saubrecht@netbeans.org> Log: #217673 - use timeout when waiting for AWT thread