Bug 295213 - aioob in DeadlockDetector.java:335
Summary: aioob in DeadlockDetector.java:335
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-16 04:40 EST by Peter Larsen CLA
Modified: 2020-02-17 18:19 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Larsen CLA 2009-11-16 04:40:45 EST
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)
Build Identifier: I20090611-1540

ENTRY org.eclipse.core.jobs 4 2 2009-09-30 09:32:38.774
!MESSAGE LockManager.handleException
!STACK 0
java.lang.ArrayIndexOutOfBoundsException: 0
	at org.eclipse.core.internal.jobs.DeadlockDetector.lockReleased(DeadlockDetector.java:335)
	at org.eclipse.core.internal.jobs.LockManager.removeLockThread(LockManager.java:253)
	at org.eclipse.core.internal.jobs.OrderedLock.setCurrentOperationThread(OrderedLock.java:264)
	at org.eclipse.core.internal.jobs.OrderedLock.doRelease(OrderedLock.java:193)
	at org.eclipse.core.internal.jobs.OrderedLock.release(OrderedLock.java:244)
	at org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer.endOperation(EclipseSynchronizer.java:575)
	at org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer.getSyncBytes(EclipseSynchronizer.java:292)
	at org.eclipse.team.internal.ccvs.core.syncinfo.CVSBaseResourceVariantTree.getBytes(CVSBaseResourceVariantTree.java:27)
	at org.eclipse.team.internal.core.subscribers.DescendantResourceVariantByteStore.getBytes(DescendantResourceVariantByteStore.java:62)
	at org.eclipse.team.core.variants.ResourceVariantTree.hasResourceVariant(ResourceVariantTree.java:52)
	at org.eclipse.team.internal.ccvs.core.CVSSyncTreeSubscriber.isSupervised(CVSSyncTreeSubscriber.java:97)
	at org.eclipse.team.internal.ccvs.core.CVSSyncTreeSubscriber.getSyncInfo(CVSSyncTreeSubscriber.java:75)
	at org.eclipse.team.internal.ccvs.core.CVSSyncTreeSubscriber.getDiff(CVSSyncTreeSubscriber.java:149)
	at org.eclipse.team.internal.core.subscribers.SubscriberDiffTreeEventHandler.handleChange(SubscriberDiffTreeEventHandler.java:162)
	at org.eclipse.team.internal.core.subscribers.SubscriberEventHandler.collect(SubscriberEventHandler.java:219)
	at org.eclipse.team.internal.core.subscribers.SubscriberEventHandler.processEvent(SubscriberEventHandler.java:310)
	at org.eclipse.team.internal.core.BackgroundEventHandler.processEvents(BackgroundEventHandler.java:369)
	at org.eclipse.team.internal.core.BackgroundEventHandler$1.run(BackgroundEventHandler.java:203)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

!ENTRY org.eclipse.core.jobs 4 2 2009-09-30 09:32:38.790
!MESSAGE LockManager.handleException
!STACK 0
java.lang.Exception:  :: 
 OrderedLock (7), R/,
 Worker-916 :  0, 0,
 Worker-927 :  0, 1,
-------

	at org.eclipse.core.internal.jobs.LockManager.handleInternalError(LockManager.java:188)
	at org.eclipse.core.internal.jobs.LockManager.removeLockThread(LockManager.java:256)
	at org.eclipse.core.internal.jobs.OrderedLock.setCurrentOperationThread(OrderedLock.java:264)
	at org.eclipse.core.internal.jobs.OrderedLock.doRelease(OrderedLock.java:193)
	at org.eclipse.core.internal.jobs.OrderedLock.release(OrderedLock.java:244)
	at org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer.endOperation(EclipseSynchronizer.java:575)
	at org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer.getSyncBytes(EclipseSynchronizer.java:292)
	at org.eclipse.team.internal.ccvs.core.syncinfo.CVSBaseResourceVariantTree.getBytes(CVSBaseResourceVariantTree.java:27)
	at org.eclipse.team.internal.core.subscribers.DescendantResourceVariantByteStore.getBytes(DescendantResourceVariantByteStore.java:62)
	at org.eclipse.team.core.variants.ResourceVariantTree.hasResourceVariant(ResourceVariantTree.java:52)
	at org.eclipse.team.internal.ccvs.core.CVSSyncTreeSubscriber.isSupervised(CVSSyncTreeSubscriber.java:97)
	at org.eclipse.team.internal.ccvs.core.CVSSyncTreeSubscriber.getSyncInfo(CVSSyncTreeSubscriber.java:75)
	at org.eclipse.team.internal.ccvs.core.CVSSyncTreeSubscriber.getDiff(CVSSyncTreeSubscriber.java:149)
	at org.eclipse.team.internal.core.subscribers.SubscriberDiffTreeEventHandler.handleChange(SubscriberDiffTreeEventHandler.java:162)
	at org.eclipse.team.internal.core.subscribers.SubscriberEventHandler.collect(SubscriberEventHandler.java:219)
	at org.eclipse.team.internal.core.subscribers.SubscriberEventHandler.processEvent(SubscriberEventHandler.java:310)
	at org.eclipse.team.internal.core.BackgroundEventHandler.processEvents(BackgroundEventHandler.java:369)
	at org.eclipse.team.internal.core.BackgroundEventHandler$1.run(BackgroundEventHandler.java:203)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Reproducible: Didn't try
Comment 1 John Arthorne CLA 2009-11-16 10:09:50 EST
Similar to bug 155896.
Comment 2 Peter Larsen CLA 2009-11-16 10:29:28 EST
I found no OutOfMemoryError in this session.
Comment 3 James Blackburn CLA 2010-11-26 05:17:46 EST
Similar to: Bug 329090
Comment 4 Szymon Ptaszkiewicz CLA 2012-06-26 08:45:14 EDT
The exception says "ArrayIndexOutOfBoundsException: 0" which means threadIndex or lockIndex was equal to 0 and it was already out of range, so the graph must have been empty. This information collides with the debug string where we see that the graph size was 2x2 so index equal to 0 should be valid. The only explanation that I can think of is that handleInternalError() is called outside of the synchroznied block so before debug string is taken, the state of deadlock detector may change thus resulting in incompatible debug string. See bug 383546.
Comment 5 Eclipse Genie CLA 2020-02-17 18:19:47 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.