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 181869 - LowPerformance took 98408 ms.
Summary: LowPerformance took 98408 ms.
Status: RESOLVED WORKSFORME
Alias: None
Product: editor
Classification: Unclassified
Component: Parsing & Indexing (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Tomas Zezula
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2010-03-11 09:41 UTC by Exceptions Reporter
Modified: 2012-03-20 09:27 UTC (History)
10 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 156404

Attachments
nps snapshot (256.00 KB, application/nps)
2010-03-11 09:41 UTC, Exceptions Reporter 		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 Exceptions Reporter 2010-03-11 09:41:24 UTC 
Build: NetBeans IDE Dev (Build 201001271614)
VM: Java HotSpot(TM) 64-Bit Server VM, 16.0-b13, Java(TM) SE Runtime Environment, 1.6.0_18-b07
OS: Windows 7

User Comments:
johnny_bit: writing 'cat' then doing ctrl+space

jirka_x1: Typing: 
log.info("TEST UPLOAD"); 

(probably the string parameter)

GUEST: Waiting for methods list for object

GUEST: autocomplete



Maximum slowness yet reported was 98408 ms, average is 20110
Comment 1 Exceptions Reporter 2010-03-11 09:41:32 UTC 
Created attachment 95055 [details]
nps snapshot
Comment 2 Dusan Balek 2010-05-05 15:17:27 UTC 
TaskProcessor seems to be blocked by synchronous call to FileUtil.refreshAll() from ReposrityUpdater.
Comment 3 Vitezslav Stejskal 2010-05-11 13:25:49 UTC 
(In reply to comment #2)
> TaskProcessor seems to be blocked by synchronous call to FileUtil.refreshAll()
> from ReposrityUpdater.

Really? I went through the last ~4 snapshots and the templates expansion was blocked by ordinary scanning - in some cases it was actually FU.addRecursiveListener part of the scanning. Maybe, we should just use PU.runOffEventDispatchThread...
Comment 4 David Strupl 2012-03-20 09:27:56 UTC 
This report did not repeat in the recent builds --> closing as works for me.