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 21316 - ALL: Rare deadlock when changing working directory in customizer.
Summary: ALL: Rare deadlock when changing working directory in customizer.
Status: VERIFIED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcscore (show other bugs)
Version: -FFJ-
Hardware: PC Solaris
: P3 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords: THREAD
: 25946 28073 28210 (view as bug list)
Depends on: 20385
Blocks:
  Show dependency tree
 
Reported: 2002-03-07 16:12 UTC by Jiri Kovalsky
Modified: 2003-02-04 13:52 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
ThreadDump taken while IDE was hanging. (26.66 KB, text/plain)
2002-03-07 16:14 UTC, Jiri Kovalsky 		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 Jiri Kovalsky 2002-03-07 16:12:36 UTC 
EAP RC3 build #020306 of Forte for Java 4.0 on Solaris 5.8 with JDK 1.4 b92

Description:
============
I have already encountered several times a deadlock when I was trying to change
the working directory of already mounted filesystem. I also want to add that in
both cases I had relative mount point set. However I can't reproduce it on dema-
nd. Have a look at full thread dump attached.

Here is what I do:
==================
1. Mount CVS filesystem with complex directory structure and set relative mount
   point to some subdirectory.
2. After some minor work invoke the customizer and try to change the working dir- 
   ectory through the browser.
3. Immediately after clicking "Open" button the IDE freezed.
Comment 1 Jiri Kovalsky 2002-03-07 16:14:46 UTC 
Created attachment 4991 [details]
ThreadDump taken while IDE was hanging.
Comment 2 Martin Entlicher 2002-03-07 17:47:15 UTC 
The problem is, that the commands are stored in Nodes hierarchy. This
cause problems when another thread plays with Nodes at the same time.
This will be solved after the new VCS APIs will be used.
Comment 3 Martin Entlicher 2002-05-16 11:26:59 UTC 
This is a quite rare bug, which would be solved by the implementation
of VCS APIs. However the VCS APIs were postponed to 4.0.

Does anybody still get this deadlock sometimes or did it disappear??
The fix of 3.4 would be possible without the APIs, but not trivial.
Looking for any comments on whether it's worth to fix it now or
whether it's O.K. to wait for 4.0.
Comment 4 Jiri Kovalsky 2002-05-16 12:09:51 UTC 
To be honest, I didn't see it for quite some time but on the other
hand didn't search it intentionally ... :-) However, I know that David
Kaspar warned me about certain deadlocks recently. Can you Davide
comment on this ?
Comment 5 Milos Kleint 2002-07-09 14:42:39 UTC 
postponing to 4.0 regarding to the comments..
Comment 6 Martin Entlicher 2002-07-24 16:48:14 UTC 
*** Issue 25946 has been marked as a duplicate of this issue. ***
Comment 7 Martin Entlicher 2002-10-17 11:40:07 UTC 
*** Issue 28073 has been marked as a duplicate of this issue. ***
Comment 8 Martin Entlicher 2002-10-23 13:37:08 UTC 
*** Issue 28210 has been marked as a duplicate of this issue. ***
Comment 9 Martin Entlicher 2002-11-01 16:45:39 UTC 
Fixed in the main trunk.
The VCS APIs were just merged into the main trunk. Their
implementation solve this problem.
Comment 10 Jiri Kovalsky 2002-11-08 08:45:03 UTC 
I hope I won't see this again. :-) Verified in development build
#200211080100 of NetBeans 4.0.