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 28210

Summary:	Deadlock while selecting items in the Filesystems \| Mount menu
Product:	obsolete	Reporter:	Jan Chalupa <jchalupa>
Component:	vcscore	Assignee:	issues@obsolete <issues>
Status:	VERIFIED DUPLICATE
Severity:	blocker	Keywords:	RANDOM, THREAD
Priority:	P2
Version:	3.x
Hardware:	PC
OS:	Windows 3.1/NT
Issue Type:	DEFECT	Exception Reporter:
Attachments:	Tread dump

Description Jan Chalupa 2002-10-23 11:35:53 UTC

[dev-20021023, Sun JDK 1.4.1_01, MDI]

1. mounted a local filesystem and jar into the
repository.
2. was about to add another jar file
3. right-clicked on the Filesystems node, selected
Mount
4. moved mouse over the Mount submenu
5. before I could select the Jar File item, IDE
deadlocked

Thread dump will be attached shortly. Two
suspicious threads seem to be doing something with
VCS. Note that I didn't have any VCS filesystems
mounted and I didn't want to mount one. Feel free
to re-assign if not in VCS.

Comment 1 Jan Chalupa 2002-10-23 11:36:32 UTC

Created attachment 7750 [details]
Tread dump

Comment 2 Jiri Kovalsky 2002-10-23 12:13:56 UTC

I would argue that this is P2. According to
http://qa.netbeans.org/processes/bug_priority_guidelines.html it
should happen fairly often, which is not the case right ? Would you
mind Honzo to downgrade it ? Isn't it rather performance issue ? What
do you think Martin ?

Comment 3 Jan Chalupa 2002-10-23 13:02:51 UTC

Yes, I would mind downgrading it to P3. According to the guidelines, a
reliably reproducible deadlock is a P1. Intermittent deadlock is a P2.

I have no evidence how frequently it occurs, but the facts that it
occured once and a thread dump is available should be good reasons to
get if fixed quickly. After all, every deadlock is a potential data loss.

Comment 4 Martin Entlicher 2002-10-23 13:37:12 UTC

This is basically a duplicate of issue #21316.
The problem is, that FS commands are stored in Nodes hierarchy.

The performance problem could be, that somebody is trying to
instantiate my filesystem. I would say, that this is a problem of
core. Should we file a PERFORMANCE defect for this?


*** This issue has been marked as a duplicate of 21316 ***

Comment 5 Martin Entlicher 2002-10-23 13:46:05 UTC

*** Issue 28207 has been marked as a duplicate of this issue. ***

Comment 6 Martin Entlicher 2002-10-23 13:46:07 UTC

*** Issue 28205 has been marked as a duplicate of this issue. ***

Comment 7 Jiri Kovalsky 2002-11-08 10:40:08 UTC

I have seen this yesterday too, which means that fixing #21316 didn't
help. If you could Martin file something against core, I would
appreciate it. Thanks ! Verified in development build #200211080100 of
NetBeans 4.0.

Comment 8 Martin Entlicher 2002-11-08 18:24:26 UTC

> I have seen this yesterday too, which means that fixing #21316
> didn't help.

What do you mean by 'this'? The exactly same stack trace? I don't
believe. Can you attach the full thread dump please?

> If you could Martin file something against core, I would appreciate
> it.

Something?? It did not hapen to me! ;-) So I don't know where the
problem is.

Comment 9 Jiri Kovalsky 2002-11-11 08:09:02 UTC

By "this" I mean a deadlock while opening "Filesystems|Mount ..."
popup menu. I am sorry, I didn't manage to capture the thread dump.
I'll do this next time I see it. :)