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 57316 - DeadLock after/during code completition
Summary: DeadLock after/during code completition
Status: VERIFIED FIXED
Alias: None
Product: editor
Classification: Unclassified
Component: Completion & Templates (show other bugs)
Version: 4.x
Hardware: All All
: P1 blocker (vote)
Assignee: Miloslav Metelka
URL:
Keywords:
: 57354 57371 57461 57643 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-04-01 12:16 UTC by Martin Krauskopf
Modified: 2007-11-05 13:38 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
thread dump (11.75 KB, text/plain)
2005-04-01 12:18 UTC, Martin Krauskopf 		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 Martin Krauskopf 2005-04-01 12:16:29 UTC 
Build 050401, 1.5.0_02-b09, FC2

Steps to reproduce:

1) Run IDE with clean USER_DIR
2) Open "openide" module
3) Open PSheet class (Ctrl-Shift-o --> PSheet)
4) Enter new line into (e.g.) PSheet constructor
5) Type Utiliti<press space>
6) Choose our org.openide.util.Utilities<press enter>
7) Wait cca from 0.5 to 2 seconds
8) DeadLock

Thread dump attachment follows.

It probably doesn't matter which class but it seems it has to be "our" module
from. In my own simple module it works. Don't know why...
Comment 1 Martin Krauskopf 2005-04-01 12:18:32 UTC 
Created attachment 21285 [details]
thread dump
Comment 2 Miloslav Metelka 2005-04-01 12:46:10 UTC 
It's document lock against awt tree lock. I'll investigate.
Comment 3 Miloslav Metelka 2005-04-01 14:25:10 UTC 
Fixed in main trunk:
Checking in libsrc/org/netbeans/editor/BaseCaret.java;
/cvs/editor/libsrc/org/netbeans/editor/BaseCaret.java,v  <--  BaseCaret.java
new revision: 1.111; previous revision: 1.110
Comment 4 Miloslav Metelka 2005-04-04 09:23:53 UTC 
*** Issue 57354 has been marked as a duplicate of this issue. ***
Comment 5 Miloslav Metelka 2005-04-04 09:24:56 UTC 
Unfortunately this issue was a regression caused by integration of fix for issue
35034.
Comment 6 Miloslav Metelka 2005-04-04 09:25:41 UTC 
*** Issue 57354 has been marked as a duplicate of this issue. ***
Comment 7 Miloslav Metelka 2005-04-04 09:51:31 UTC 
*** Issue 57371 has been marked as a duplicate of this issue. ***
Comment 8 Miloslav Metelka 2005-04-05 09:58:45 UTC 
*** Issue 57461 has been marked as a duplicate of this issue. ***
Comment 9 Dusan Balek 2005-04-08 07:23:30 UTC 
*** Issue 57643 has been marked as a duplicate of this issue. ***
Comment 10 Roman Strobl 2005-07-14 14:01:03 UTC 
Martine, can you please verify this issue? Thanks.
Comment 11 Roman Strobl 2005-10-26 20:51:15 UTC 
No response, seems to be fixed -> marking as verified.