40342 – deadlock after synchronization dialog

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 40342 - deadlock after synchronization dialog

Summary: deadlock after synchronization dialog

Status:	VERIFIED FIXED

Alias:	None

Product:	java
Classification:	Unclassified
Component:	Unsupported (show other bugs)
Version:	3.x
Hardware:	PC Windows XP

Importance:	P2 blocker (vote)
Assignee:	Jan Pokorsky

URL:
Keywords:	RANDOM, THREAD

Duplicates (1):	40749 (view as bug list)
Depends on:
Blocks:

Reported:	2004-02-21 01:38 UTC by _ jrichard
Modified:	2007-09-26 09:14 UTC (History)
CC List:	2 users (show)

See Also:
Issue Type:	DEFECT
Exception Reporter:

Attachments
dump after freeze (13.76 KB, text/plain) 2004-02-21 01:39 UTC, _ jrichard	Details
original dump.txt with newlines preserved (14.13 KB, text/plain) 2004-02-21 13:50 UTC, _ jrichard	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 _ jrichard 2004-02-21 01:38:05 UTC

After creating a new class and typing "extends
MySuperClass" and saving, the synchronization
dialog popped up.  When it did I selected the
option to process all, netbeans proceeded to hang.

I'll attach a thread dump.

Comment 1 _ jrichard 2004-02-21 01:39:18 UTC

Created attachment 13557 [details]
dump after freeze

Comment 2 Marian Mirilovic 2004-02-21 08:24:35 UTC

John,
I am sorry, but your thread-dump is unreadable, I have seen whole
stack trace on one line, please attach thread-dump again with
appropriate text wrapping.

By the way another information we need too, like JDK, IDE build
number, ......

If you'll attach new infromations REOPEN, thanks in advance.

Comment 3 _ jrichard 2004-02-21 13:45:07 UTC

Oops.

NetBeans build: dev 20040219

JDK: Java HotSpot(TM) Client VM (1.4.2_01-b06 mixed mode)

Comment 4 _ jrichard 2004-02-21 13:50:01 UTC

Created attachment 13558 [details]
original dump.txt with newlines preserved

Comment 5 _ jrichard 2004-02-21 13:53:37 UTC

It doesn't always reproduce, but seems to happen more frequently with
a base class with a bunch of abstract methods.

Comment 6 Marian Mirilovic 2004-02-21 13:56:57 UTC

Thanks a lot

Comment 7 Miloslav Metelka 2004-02-23 10:49:57 UTC

It is likely a java module's problem as all the involved threads deal
with java-related operation but I did not examine the details.
Reassigning to java module.

Comment 8 Jan Pokorsky 2004-02-25 14:51:19 UTC

Yes, it is a java stuff. The code-sync support calls
ClassElement.forName under a document write lock which is required
later in the parser thread too.

Comment 9 Jan Pokorsky 2004-03-01 15:44:11 UTC

Please try to reproduce it with the latest developer build. There were
made changes in threading model. It could also help if you can provide
your sources on which you can reproduce this.

Comment 10 Jan Pokorsky 2004-03-08 15:49:56 UTC

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

Comment 11 Jan Pokorsky 2004-03-09 16:07:41 UTC

Tome, could you review the fix so I can ask for integration to releas36?

Fixed in trunk:
http://www.netbeans.org/source/browse/java/src/org/netbeans/modules/java/codesync/ClassDependencyImpl.java.diff?r1=1.30&r2=1.31&f=u
http://www.netbeans.org/source/browse/java/src/org/netbeans/modules/java/tools/InheritanceSupport2.java.diff?r1=1.1&r2=1.2&f=u

Comment 12 Tomas Hurka 2004-03-09 17:03:10 UTC

I looked at the diffs and I think that the fix is correct.

Comment 13 Jan Pokorsky 2004-03-09 17:31:25 UTC

Thanks. I notified reviewers@netbeans.org

Comment 14 Jan Pokorsky 2004-03-10 17:16:35 UTC

No objection -> merged to release36

/cvs/java/src/org/netbeans/modules/java/tools/InheritanceSupport2.java,v1.1.20.1
/cvs/java/src/org/netbeans/modules/java/codesync/ClassDependencyImpl.java,v1.30.16.1

Comment 15 Jiri Prox 2005-07-14 11:17:52 UTC

Verified