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 180756 - [69cat] Palette content created in AWT
Summary: [69cat] Palette content created in AWT
Status: RESOLVED FIXED
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: issues@guibuilder
URL:
Keywords: PERFORMANCE
: 182132 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-02-15 19:42 UTC by Exceptions Reporter
Modified: 2011-02-01 16:54 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 162927


Attachments
nps snapshot (256.00 KB, application/nps)
2010-02-15 19: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 2010-02-15 19:42:36 UTC
Build: NetBeans IDE 6.8 (Build 200912041610)
VM: Java HotSpot(TM) Client VM, 11.3-b02, Java(TM) SE Runtime Environment, 1.6.0_13-b03
OS: Windows XP

User Comments:
GUEST: Updating plugins from version 6.7



Maximum slowness yet reported was 25296 ms, average is 8265
Comment 1 Exceptions Reporter 2010-02-15 19:42:42 UTC
Created attachment 94179 [details]
nps snapshot
Comment 2 Tomas Pavek 2010-02-16 11:22:58 UTC
Reveals slow palette content creation (i.e. loading classes and BeanInfos for items in palette). The snapshots show various origin - (1) showing the palette, (2) expanding some category, (3) finding layouts in the palette (for Set Layout action or when a custom layout manager is used in a loaded form).

(1) and (2) could possibly be done on background, updating the palette when complete.

(3) must be done synchronously when the GUI builder needs to find out what layout managers are registered in the palette. Here some faster way of determining this would be desirable.
Comment 3 Jan Stola 2010-03-16 16:25:10 UTC
*** Bug 182132 has been marked as a duplicate of this bug. ***
Comment 4 Tomas Pavek 2011-02-01 16:54:43 UTC
Palette loading was re-planned off AWT thread, I think for 6.9.

It became a great source of deadlocks when the bug in JDK 6 u21 and u22 appeared, see bug 187697.

Anyway, I think we can mark this as fixed.