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.

Bug 188172 - 5s - blocked by AbstractDocument.writeLock()
Summary: 5s - blocked by AbstractDocument.writeLock()
Status: RESOLVED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: Embedded Browser (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Stanislav Aubrecht
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2010-06-28 20:58 UTC by Jesse Glick
Modified: 2012-05-24 12:33 UTC (History)
25 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 170937


Attachments
nps snapshot (67.92 KB, application/nps)
2010-06-28 20:59 UTC, Jesse Glick
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2010-06-28 20:58:55 UTC
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
Comment 1 Jesse Glick 2010-06-28 20:59:02 UTC
Created attachment 100468 [details]
nps snapshot
Comment 2 Jaroslav Tulach 2010-06-29 09:20:07 UTC
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.
Comment 3 Jesse Glick 2010-06-29 13:49:43 UTC
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.
Comment 4 velodiver 2010-11-23 14:40:29 UTC
I got this error using 7.0 beta.
Comment 5 Stanislav Aubrecht 2012-05-24 12:30:46 UTC
The last report is more than two years old, closing.