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 173844 - [68cat] AWT thread blocked for 3219 ms.
Summary: [68cat] AWT thread blocked for 3219 ms.
Status: RESOLVED WONTFIX
Alias: None
Product: web
Classification: Unclassified
Component: CSS Visual Tools (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Marek Fukala
URL: http://statistics.netbeans.org/except...
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2009-10-06 10:42 UTC by Exceptions Reporter
Modified: 2009-10-06 11:03 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 156073


Attachments
nps snapshot (15.10 KB, bin/nps)
2009-10-06 10:42 UTC, Exceptions Reporter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2009-10-06 10:42:45 UTC
Build: NetBeans IDE Dev (Build 200908022240)
VM: Java HotSpot(TM) Client VM, 11.2-b01, Java(TM) SE Runtime Environment, 1.6.0_12-b04
OS: Windows XP, 5.1, x86

User Comments:
mkroll: Using the editor

GUEST: opening a php file from a php project

GUEST: I don't know, I am getting this message frequently


Maximum slowness yet reported was 8055 ms, average is 4552
Comment 1 Exceptions Reporter 2009-10-06 10:42:50 UTC
Created attachment 88890 [details]
nps snapshot
Comment 2 Exceptions Reporter 2009-10-06 10:42:56 UTC
This issue already has 6 duplicates 
see http://statistics.netbeans.org/exceptions/detail.do?id=156073
Comment 3 Marek Fukala 2009-10-06 11:03:05 UTC
There are two different issues mixed in the reports: 

The first one is that java.awt.Font.getFamily() is called in AWT, but the method can be very slow. This issue has
already been fixed.

Second problem is that the XHTML renderer initialization can take a longer time in AWT, which I cannot influence much.