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

Summary:	[73cat] CodeCompletion took 2030 ms.
Product:	debugger	Reporter:	misterm <misterm>
Component:	Java	Assignee:	Martin Entlicher <mentlicher>
Status:	RESOLVED WONTFIX
Severity:	normal	Keywords:	PERFORMANCE
Priority:	P3
Version:	7.4
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:	198190
Attachments:	nps snapshot

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.