48382 – Deadlock running automated tests

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 48382 - Deadlock running automated tests

Summary: Deadlock running automated tests

Status:	RESOLVED FIXED

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	UI (show other bugs)
Version:	3.0
Hardware:	PC Windows 2000

Importance:	P3 critical (vote)
Target Milestone:	---
Assignee:	Stefan Xenos
QA Contact:

URL:
Whiteboard:
Keywords:

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

Reported:	2003-12-09 19:14 EST by John Arthorne
Modified:	2004-01-07 18:55 EST (History)
CC List:	3 users (show)

See Also:

Attachments
Automated test console output (15.61 KB, text/plain) 2003-12-09 19:14 EST, John Arthorne	no flags	Details
This should fix it (4.31 KB, application/octet-stream) 2003-12-09 21:42 EST, Stefan Xenos	no flags	Details
View All 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 John Arthorne

2003-12-09 19:14:18 EST

I20031209

The automated tests for this build failed due to a deadlock.  The stack trace is
attached.  All of the jobs involved are from the new marker view work.  The
problematic pattern is in Worker-4 and Worker-1, both of which are trying to
join another job while owning an ILock.  I recommend releasing the ILock before
attempting to join the job.

Comment 1 John Arthorne

2003-12-09 19:14:43 EST

Created attachment 7095 [details]
Automated test console output

Comment 2 Stefan Xenos

2003-12-09 21:42:43 EST

Created attachment 7096 [details]
This should fix it

The lock is no longer retained through a join operation.

Comment 3 Tod Creasey

2003-12-10 09:03:27 EST

I have released the fix but we still need to verify using the JDT suites.

Comment 4 Stefan Xenos

2003-12-10 13:21:21 EST

*** Bug 48396 has been marked as a duplicate of this bug. ***

Comment 5 Stefan Xenos

2004-01-07 18:28:57 EST

John, can you verify if this is fixed?

Comment 6 John Arthorne

2004-01-07 18:50:41 EST

I never reproduced this personally.  I think the fact that it has not failed
again in three weeks of builds suggests that this is fixed.

Comment 7 Stefan Xenos

2004-01-07 18:55:08 EST

Thanks. Please reopen if the problem recurs.