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 241761 - 10s - deserializing may TopComponents in EDT
Summary: 10s - deserializing may TopComponents in EDT
Status: RESOLVED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: Stanislav Aubrecht
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2014-02-12 12:10 UTC by misterm
Modified: 2014-03-21 10:28 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 203175


Attachments
nps snapshot (250.53 KB, application/nps)
2014-02-12 12:10 UTC, misterm
Details

Note You need to log in before you can comment on or make changes to this bug.
Description misterm 2014-02-12 12:10:48 UTC
Build: NetBeans IDE Dev (Build 20140127-bdc560a151f2)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.3-b01, Java(TM) SE Runtime Environment, 1.7.0_07-b11
OS: Windows 7

User Comments:
GUEST: 100% das vezes que inicio o NetBeans, demora 10 minutos para poder abrir o projeto, abrir o arquivo e come
Comment 1 misterm 2014-02-12 12:10:51 UTC
Created attachment 145084 [details]
nps snapshot
Comment 2 Jaroslav Tulach 2014-02-14 11:34:51 UTC
Deserialization of many TC at once takes place in EDT and blocks UI. Could possibly deserialize one TC by one in separete EventQueue.invokeLater or delay the deserialization by knowing more about the one TC which is being looked for by 
org.netbeans.core.windows.persistence.PersistenceManager.getTopComponentForID()	87.82838	9 369 ms (87,8%)	9 298 ms	1
Comment 3 Stanislav Aubrecht 2014-02-17 10:45:54 UTC
There are slowness reports unrelated to window system deserialization which indicate a possible problem in ModuleManager.SystemClassLoader.loadClass(). For example:

http://statistics.netbeans.org/exceptions/exception.do?id=691657
http://statistics.netbeans.org/exceptions/exception.do?id=700933

Please evaluate again, thanks.
Comment 4 Jaroslav Tulach 2014-02-17 16:24:43 UTC
Classloading issues are tracked by issue 241367, please ignore them and focus on the loading of multiple components in a row. Btw. issue 241367 basically suggests to remove/ignore the slow classloading issues from a database - so we can really ignore those - but the windowing snapshot is not going to be ignored, as there are multiple "call counts" into the same code - e.g. it is not slow classloading.
Comment 5 Stanislav Aubrecht 2014-03-21 10:28:36 UTC
No plans to change winsys deserialization.