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 233889 - org.netbeans.modules.editor.completion.CompletionJList.setData: LowPerformance took 3429 ms.
Summary: org.netbeans.modules.editor.completion.CompletionJList.setData: LowPerformanc...
Status: RESOLVED INCOMPLETE
Alias: None
Product: platform
Classification: Unclassified
Component: JDK Problems (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Stanislav Aubrecht
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2013-08-03 13:23 UTC by jyeary
Modified: 2013-08-19 10:07 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 202793


Attachments
nps snapshot (19.48 KB, application/nps)
2013-08-03 13:23 UTC, jyeary
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jyeary 2013-08-03 13:23:22 UTC
This bug was originally marked as duplicate of bug 219507, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 7.4 Beta (Build 201307092200)
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:
jyeary: Unknown

jyeary: Unknown



Maximum slowness yet reported was 3429 ms, average is 3356
Comment 1 jyeary 2013-08-03 13:23:24 UTC
Created attachment 138229 [details]
nps snapshot
Comment 2 Dusan Balek 2013-08-05 08:06:13 UTC
Code completion is waiting for an extremely slow call to
org.openide.util.Utilities.getUsableScreenBounds()
Comment 3 Antonin Nebuzelsky 2013-08-05 10:25:37 UTC
Some caching has been done when resolving issue 219507.

Reassigning for additional evaluation.
Comment 4 Stanislav Aubrecht 2013-08-12 11:48:05 UTC
Reporter, do you have dual screen setup?
Comment 5 Stanislav Aubrecht 2013-08-19 10:07:04 UTC
Please provide the requested info on your screen setup and reopen.
Also note that the caching added in #219507 expires after some time so it's possible that there will be some slowness when checking screen bounds occasionally.