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 176704 - AWT thread blocked for 21765 ms.
Summary: AWT thread blocked for 21765 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: 2009-11-12 09:52 UTC by ravindranathakila
Modified: 2012-03-20 08:22 UTC (History)
6 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 161834


Attachments
nps snapshot (256.00 KB, application/nps)
2009-11-12 09:52 UTC, ravindranathakila
Details
nps snapshot (23.93 KB, application/nps)
2011-09-14 06:40 UTC, wangcll
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ravindranathakila 2009-11-12 09:52:13 UTC
Build: NetBeans IDE 6.8 Beta (Build 200910212001)
VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01
OS: Windows XP, 5.1, x86

User Comments:
_m4c0_: autocompleting


Maximum slowness yet reported was 21765 ms, average is 16452
Comment 1 ravindranathakila 2009-11-12 09:52:18 UTC
Created attachment 90921 [details]
nps snapshot
Comment 2 Vitezslav Stejskal 2009-11-13 05:48:12 UTC
This seems to be between (java) code completion and hints. I don't understand why the hint task was not cancelled by the completion task, but apparently it was not.
Comment 3 lahodaj 2009-11-13 06:29:00 UTC
Well, what I do not understand in the snapshot is that TaskProcessor.runUserTask is called once (in AWT), but ParserManager$UserTaskAction is invoked 6 times from inside it. TaskProcessor.runUserTask does not seem to have any loop inside, so I do not understand this.

But, there are certainly suspicious things in the snapshot:
-when the CC is visible, no scheduled tasks should be performed, but they apparently are (and it seems that the hint is canceled and started again, as it has call count 6 - I do not fully trust the call count though, due to the call count described in the first paragraph). I will try to peek at this.
-the hints are blocked in the Lucene index - IIRC, pre-6.7, the Lucene index query itself was cancelable. Tomas, is the query still cancelable? Thanks.
Comment 4 lahodaj 2009-11-13 08:05:06 UTC
I tested the mechanism that stops the scheduled tasks when the CC is running, and it worked fine for me. I suspected that the problem could be in with a CC provider that would not support filtering, but my testing provider did not have any effect on this mechanism.
Comment 5 wangcll 2011-09-14 06:40:28 UTC
Created attachment 110728 [details]
nps snapshot
Comment 6 David Strupl 2012-03-20 08:22:02 UTC
The snapshot 176704 shows Javadoc blocking code completion. This was fixed recently afaik. The other snaphots are rather old and no new duplicate --> closing...