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 242126 - 400x ContextManager.isEnabledOnDataImpl: took 39083 ms.
Summary: 400x ContextManager.isEnabledOnDataImpl: took 39083 ms.
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Actions (show other bugs)
Version: 8.0
Hardware: All All
: P2 normal (vote)
Assignee: Jan Peska
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2014-02-20 03:22 UTC by Exceptions Reporter
Modified: 2014-07-29 02:33 UTC (History)
19 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 207802


Attachments
nps snapshot (650.55 KB, application/nps)
2014-02-20 03:22 UTC, Exceptions Reporter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2014-02-20 03:22:46 UTC
Build: NetBeans IDE 8.0 Beta (Build 201401141042)
VM: Java HotSpot(TM) 64-Bit Server VM, 24.51-b03, Java(TM) SE Runtime Environment, 1.7.0_51-b13
OS: Mac OS X

User Comments:
GUEST: Didn't respond when clicking in projects

GUEST: Opening a cucumber feature file



Maximum slowness yet reported was 39083 ms, average is 37238
Comment 1 Exceptions Reporter 2014-02-20 03:22:53 UTC
Created attachment 145423 [details]
nps snapshot
Comment 2 gooddreams 2014-04-24 03:40:26 UTC
A long time issue also in other versions. To reproduce it just open a very big project that has many classes, clean and build the project, memory use will increase to a high level, at least 1g, or even more than 2g. And then each time when you switch back to project navigation pane to click a package node (open package folder), it will no response for a long time.
Comment 3 Jan Peska 2014-07-14 11:18:50 UTC
Most of the time is spent in Lookup methods. Reassigning to Lookup for further evaluation.
Comment 4 Jaroslav Tulach 2014-07-16 13:01:32 UTC
Looking at
http://statistics.netbeans.org/exceptions/exception.do?id=730685

One call to

org.openide.explorer.DefaultEMLookup.updateLookups()	100.0	16 935 ms (100%)	16 095 ms	1

yields 42 calls to

org.openide.awt.ContextManager$LSet.resultChanged()	97.503716	16 512 ms (97,5%)	15 672 ms	42

and that triggers 400 calls to

org.openide.awt.ContextManager.isEnabledOnData()	50.3666	8 529 ms (50,4%)	8 257 ms	405
Comment 5 Jan Becicka 2014-07-25 11:59:42 UTC
about 200 reports
Comment 6 Jaroslav Tulach 2014-07-25 12:31:56 UTC
Jan, can you explain why this issue has been assigned to lookup category? What was your reasoning?
Comment 7 Jan Peska 2014-07-28 11:46:26 UTC
fix: http://hg.netbeans.org/core-main/rev/e6e65c1bd078
Comment 8 Quality Engineering 2014-07-29 02:33:25 UTC
Integrated into 'main-silver', will be available in build *201407290001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/e6e65c1bd078
User: Jan Peska <JPESKA@netbeans.org>
Log: Issue #242126 - 400x ContextManager.isEnabledOnDataImpl: took 39083 ms.
Remove also lookup result listener in LSet instances in unregisterListener method. Add tests.