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 235335 - org.netbeans.modules.cordova.platforms.api.ProcessUtilities.callProcess: LowPerformance took 11549 ms.
Summary: org.netbeans.modules.cordova.platforms.api.ProcessUtilities.callProcess: LowP...
Status: RESOLVED FIXED
Alias: None
Product: web
Classification: Unclassified
Component: Cordova (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Jan Becicka
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2013-08-30 20:01 UTC by ytn01
Modified: 2013-09-03 01:50 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 203474


Attachments
nps snapshot (105.90 KB, application/nps)
2013-08-30 20:01 UTC, ytn01
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ytn01 2013-08-30 20:01:47 UTC
This bug was originally marked as duplicate of bug 234459, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE Dev (Build 201308290001)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.25-b01, Java(TM) SE Runtime Environment, 1.7.0_25-b15
OS: Mac OS X

User Comments:
ytn01: Opened the Options dialog via Command+,
Switched to "Miscellaneous" tab
Clicked on the right arrow to navigate to next set of preference tabs,... slowness detected.



Maximum slowness yet reported was 11549 ms, average is 11549
Comment 1 ytn01 2013-08-30 20:01:51 UTC
Created attachment 139517 [details]
nps snapshot
Comment 2 Jan Becicka 2013-08-30 21:20:18 UTC
Javadoc for update method says:
Component should load its data here. You should not do any time-consuming operations inside the constructor, because it blocks initialization of OptionsDialog. Initialization should be implemented in update method.

So I do time-consuming operations in update method - but it is still called in AWT EQ. Please evaluate.
Comment 3 Theofanis Oikonomou 2013-09-02 09:43:37 UTC
(In reply to Jan Becicka from comment #2)
> Javadoc for update method says:
> Component should load its data here. You should not do any time-consuming
> operations inside the constructor, because it blocks initialization of
> OptionsDialog. Initialization should be implemented in update method.
> 
> So I do time-consuming operations in update method - but it is still called
> in AWT EQ. Please evaluate.

You should load your data in the update method but you should make sure that this is done off EDT. update() in options.api just calls each controller's update method. You know what needs to be loaded, what UI components need to be shown and how to sync the whole process. 

re-assigning back so that the loding of required data is done off EDT and the UI is then appropriately updated. Thank you
Comment 4 Jan Becicka 2013-09-02 10:44:06 UTC
Changeset: 8d05c8d1b9cf
Author:    Jan Becicka <jbecicka@netbeans.org>
Date:      2013-09-02 12:42
Message:
Comment 5 Quality Engineering 2013-09-03 01:50:35 UTC
Integrated into 'main-silver', will be available in build *201309030001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/8d05c8d1b9cf
User: Jan Becicka <jbecicka@netbeans.org>
Log: Issue #235335 - org.netbeans.modules.cordova.platforms.api.ProcessUtilities.callProcess: LowPerformance took 11549 ms.