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 236280 - [73cat] CodeCompletion took 2030 ms.
Summary: [73cat] CodeCompletion took 2030 ms.
Status: RESOLVED WONTFIX
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2013-09-23 16:42 UTC by misterm
Modified: 2014-07-16 11:30 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 198190

Attachments
nps snapshot (25.29 KB, application/nps)
2013-09-23 16:42 UTC, misterm 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description misterm 2013-09-23 16:42:37 UTC 
This issue was reported manually by misterm.
It already has 1 duplicates 


Build: NetBeans IDE Dev (Build 20130130-8551ab433946)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.3-b01, Java(TM) SE Runtime Environment, 1.7.0_07-b11
OS: Windows 7
Maximum slowness yet reported was 2030 ms, average is 2030
Comment 1 misterm 2013-09-23 16:42:39 UTC 
Created attachment 140385 [details]
nps snapshot
Comment 2 Martin Entlicher 2013-09-23 21:19:58 UTC 
There's apparently something wrong with this snapshot. It does not have 2030 ms, but only 1249 ms. And 1187 ms from that is spent in java.awt.EventQueue.getNextEvent()

Moving to profiler to evaluate what's going on and why this was submitted.
Comment 3 Martin Entlicher 2013-09-23 21:22:32 UTC 
Ah, now I've realized this is a special code-completion snapshot, not a general slowness.
Comment 4 Ondrej Vrabec 2014-07-16 11:30:02 UTC 
just slightly over 1s in
Code Completion	100.0	1,249 ms (100%)	1,249 ms
does not look that much of a problem.