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.
Build: NetBeans IDE Dev (Build 100303-c2df0a095cce) VM: Java HotSpot(TM) Client VM, 1.6.0_05-ea-b04, Java(TM) SE Runtime Environment, 1.6.0_05-ea-b04 OS: Linux Maximum slowness yet reported was 80161340 ms, average is 80161340
Created attachment 94802 [details] nps snapshot
The code completion certainly did not take 80161340ms (more than 22 hours). I used CC many times on many files in last 22 hours. So this seems like a bug in the time measurement, which needs to be fixed.
Created attachment 94818 [details] nps snapshot
The problem with incorrect times was fixed by Jarda in 9bdb5c4590e7.
As # 353776 shows, the issue hasn't been resolved yet.
(In reply to comment #5) > As # 353776 shows, the issue hasn't been resolved yet. Same for # 354697
core-main#771ae58c5840
Integrated into 'main-golden', will be available in build *201003260201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/771ae58c5840 User: Jaroslav Tulach <jtulach@netbeans.org> Log: #181584: I have to say I don't know where the huge numbers come from, but at least let's sieve them out
This simply means code completion slowness reports won't get generated anymore, since all the ones that I've got for around two weeks showed the wrong time when submitted, but showed the right time on the status bar. Is it really what you want?