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 192823 - [70cat][editor] Code Completion dialog is delayed in closing. Causes delay in keystroke processing.
Summary: [70cat][editor] Code Completion dialog is delayed in closing. Causes delay i...
Status: RESOLVED INCOMPLETE
Alias: None
Product: editor
Classification: Unclassified
Component: Completion & Templates (show other bugs)
Version: 7.0
Hardware: All All
: P3 normal (vote)
Assignee: Dusan Balek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-03 01:43 UTC by esmithbss
Modified: 2010-12-03 08:32 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description esmithbss 2010-12-03 01:43:01 UTC
Product Version = NetBeans IDE Dev (Build 201012020001)
Operating System = Windows XP version 5.1 running on x86
Java; VM; Vendor = 1.6.0_20
Runtime = Java HotSpot(TM) Client VM 16.3-b01

During editing of a file, I paused after adding a few characters to a line and invoking code completion.  The "Please Wait..." tip was displayed, but didn't resolve within a few seconds (it was still processing).

I began typing to complete the line and reached the end of the line while the tip was still displayed.  The line was :

	if ( metaData.getJoins() != null ) {

The code completion was invoked at the period between metaData and getJoins() and remained on the screen until I had completed typing the entire line and multiple characters from the next line.

All keystrokes up to the carriage return were processed immediately; however, the keystrokes after the <CR> were delayed until the tip was removed from the screen (about 5 seconds after hitting the <Enter> key).

It appears that the Code Completion tip window is delaying the processing of the carriage return.
Comment 1 Dusan Balek 2010-12-03 08:32:10 UTC
Unfortunately, I cannot reproduce the problem. Could you please create a thread dump after hitting the <Enter> key (or better profiler snapshot of the whole action) when it happens again and attach it to the issue? Thanks.