This bug was originally marked as duplicate of bug 177784, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.
Build: NetBeans IDE Dev (Build 201204220400)
VM: Java HotSpot(TM) Client VM, 20.6-b01, Java(TM) SE Runtime Environment, 1.6.0_31-b05
OS: Windows Vista
Maximum slowness yet reported was 4144 ms, average is 4144
Created attachment 118674 [details]
org.netbeans.modules.editor.MainMenuAction$FormatAction.getGlobalKitAction() 98.99213 3 978 ms (99%) 0,000 ms 1
while calling into
org.openide.filesystems.DefaultAttributes.readAttribute() 98.99213 3 978 ms (99%) 0,000 ms 1
meanwhile in parsing API:
org.netbeans.modules.html.editor.hints.HtmlHintsProvider.computeErrors() 100.0 4 018 ms (100%) 4 018 ms 1
and in pending refresh:
org.netbeans.modules.maven.j2ee.web.WebCopyOnSave$FileListenerImpl.fileDeleted() 30.46182 1 224 ms (30,5%) 1 224 ms 74
org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObjectKeeper.fileDeleted() 14.052246 564 ms (14,1%) 564 ms 53
org.netbeans.modules.parsing.impl.indexing.errors.ErrorAnnotator$RootAddedDeletedListener.fileDeleted() 10.303086 414 ms (10,3%) 414 ms 42
One report only. Not much to do with this case anyway.
Please reevaluate bug (10 duplicates).
In case of
the EDT waits for attributes which seem to be read by parsing thread:
org.netbeans.core.startup.layers.LocalFileSystemEx$DelegatingAttributes.readAttribute() 100.0 11,238 ms (100%) 11,238 ms 1
The same applies to
just the background thread is Palette Switch:
org.netbeans.core.startup.layers.LocalFileSystemEx$DelegatingAttributes.readAttribute() 100.0 7,191 ms (100%) 7,191 ms
The parsing thread is busy with parsing about 14 editor XML files. The EDT is blocked in DefaultAttributes which seem to be processed by "main-class-updater" thread.
The problem is that org.openide.xml.XMLUtil.createXMLReader() is synchronized and that org.apache.xerces.parsers.ObjectFactory.findJarServiceProvider() seems to open (all!?) JARs to find out where XML reader provider is.
In any case this looks like an overloaded system with slow classloading. Making P4. Possible fix might be the make XMLUtils more efficient. Moving to other category.