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.
Build: NetBeans IDE Dev (Build 100624-5978557604de) VM: Java HotSpot(TM) Client VM, 16.3-b01, Java(TM) SE Runtime Environment, 1.6.0_20-b02 OS: Linux User Comments: jglick: Clicked web hyperlink in popup Javadoc from code completion. jocke: AWT event queue clocked in custom action, not NetBeans bug Maximum slowness yet reported was 10368 ms, average is 6469
Created attachment 100468 [details] nps snapshot
The snaphot shows that AWT thread waits in AbstractDocument.readLock multiple times. There is "Thread-194" which holds writeLock for multiple times (once 1.5s, once 400ms). The possible fix would be to wait while "Thread-194" finishes and only then start to render the component. I am not sure who starts the "Thread-194" however, my guess is that this somehow relates to internal HTML browser. Passing there.
Is this really the right component? I don't use the embedded browser; the HTML was being rendered by Swing as part of code completion Javadoc.
I got this error using 7.0 beta.
The last report is more than two years old, closing.