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.
... org.openide.loaders.DataFolder.getChildren(DataFolder.java:245) org.netbeans.modules.editor.NbToolbarSupport.getToolbarObjects(NbToolbarSupport.java:820) org.netbeans.modules.editor.NbToolbarSupport.addPresenters(NbToolbarSupport.java:726) org.netbeans.modules.editor.NbToolbarSupport.refreshToolbarComponent(NbToolbarSupport.java:694) org.netbeans.modules.editor.NbToolbarSupport.refreshToolbar(NbToolbarSupport.java:543) org.netbeans.modules.editor.NbToolbarSupport.access$1200(NbToolbarSupport.java:94) org.netbeans.modules.editor.NbToolbarSupport$7.propertyChange(NbToolbarSupport.java:289) java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:252) org.netbeans.core.windows.RegistryImpl.topComponentActivated(RegistryImpl.java:245) ...
Created attachment 7907 [details] Commented thread dump
Comments: This is a bit overstated. Painting is I/O as well and you can't get away without it. Icon loading is I/O and you'll need to do it from there sometimes. Bundle loading is I/O and is _usually_ done from AWT. ... _Expensive_ I/O must not be done from AWT, that's it. The problem here is that I/O was blocked by something else (a bug in automount) and that caused the editor was caught in otherwise quite fast I/O, by the way during opening of the editor, where there is pleny of other I/O anyway. Blame the automount (as I explained in the nbdev message), not editor this time.
IMHO it is fine to access java.io.File (directly or indirectly) from AWT, unless you have a specific reason to believe that the access will be significantly slow. Most apps pause if you have a bad, slow network disk. It is expected. Obviously making explicit network connections (e.g. HTTP) should never be done from the AWT thread.
Generally agree, but in this case it proved to cause problem that can be solved by asynchronous call followed by invokeLater.
Nenik was right, Automonter is the key.
Hehe, how can both of you can be sure that the problem in in Automount? The problem is IMHO in FolderList. Moreover I think that this is the same problem as 29839. Making this duplicate (although this is a bit older but the other issue is a defect which more correctly describes the situation). *** This issue has been marked as a duplicate of 29839 ***