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 18183 - Sometimes deadlock occured
Summary: Sometimes deadlock occured
Status: CLOSED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: corba (show other bugs)
Version: 3.x
Hardware: Sun SunOS
: P2 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-29 09:52 UTC by David Kaspar
Modified: 2003-06-30 17:07 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
1. (13.78 KB, text/plain)
2001-11-29 10:00 UTC, David Kaspar
Details
2. (22.25 KB, text/plain)
2001-11-29 10:00 UTC, David Kaspar
Details
3. - Last occurence (16.15 KB, text/plain)
2001-11-29 10:01 UTC, David Kaspar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Kaspar 2001-11-29 09:52:01 UTC
This deadlock is hard to reproduce.
It occures after long work of automated tests.
In the attachment there are 3 Full Thread Dumps.

Last time it happened when all automated tests finished and I did these actions:
Expand some filesystem node in the Explorer.
ERROR - Explorer did not show any sub node of this filesystem although in the
directory there was some files.
Close Source Editor window.
ERROR - Deadlock occured
Comment 1 David Kaspar 2001-11-29 10:00:22 UTC
Created attachment 3615 [details]
1.
Comment 2 David Kaspar 2001-11-29 10:00:59 UTC
Created attachment 3616 [details]
2.
Comment 3 David Kaspar 2001-11-29 10:01:37 UTC
Created attachment 3618 [details]
3. - Last occurence
Comment 4 Tomas Zezula 2001-12-04 13:04:39 UTC
Racecondition in IDLDataObject causes DeadLock of the whole IDE. So,
the priority changed to P2.
Comment 5 Tomas Zezula 2001-12-04 14:50:49 UTC
The deadlock is caused due to fileChanged after the parse thread
changed  the status of data object to STATUS_OK || STATUS_ERROR and
before the wainting thread in the method getPossibleNames reads the
value of status. This scenerio causes lost of the notification.
Comment 6 Tomas Zezula 2001-12-05 10:42:40 UTC
Fixed by removing the invalid state from the IDLDataObject.
Comment 7 David Kaspar 2002-04-05 11:46:22 UTC
Verified - No deadlock occured for a long time.
Comment 8 Quality Engineering 2003-06-30 17:07:41 UTC
Resolved for 3.3.x or earlier, no new info since then -> closing.