Bug 401421 - Deadlock in JDIThread.suspendedByVM/JDIThread.resumedByVM
Summary: Deadlock in JDIThread.suspendedByVM/JDIThread.resumedByVM
Status: CLOSED DUPLICATE of bug 325426
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.8.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-21 07:40 EST by Heiko Böttger CLA
Modified: 2013-04-19 09:25 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Heiko Böttger CLA 2013-02-21 07:40:36 EST
My eclipse is hanging during debugging, after attaching Yourkit Profiler it tells me that there is a deadlock:


Worker-220 is waiting to lock org.eclipse.jdt.internal.debug.core.model.JDIThread@7bbde9e2 which is held by Worker-225
Worker-225 is waiting to lock org.eclipse.jdt.internal.debug.core.model.JDIThread@2fca2279 which is held by Worker-220


Thread stacks


Worker-220 [BLOCKED; waiting to lock org.eclipse.jdt.internal.debug.core.model.JDIThread@7bbde9e2]
org.eclipse.jdt.internal.debug.core.model.JDIThread.suspendedByVM(JDIThread.java)
org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.suspendThreads(JDIDebugTarget.java:1312)
org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.prepareToSuspendByBreakpoint(JDIDebugTarget.java:1335)
org.eclipse.jdt.internal.debug.core.model.JDIThread.handleSuspendForBreakpoint(JDIThread.java:1107)
org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.suspend(JavaBreakpoint.java:363)
org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.handleBreakpointEvent(JavaBreakpoint.java:351)
org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.handleEvent(JavaBreakpoint.java:288)
org.eclipse.jdt.internal.debug.core.EventDispatcher.dispatch(EventDispatcher.java:154)
org.eclipse.jdt.internal.debug.core.EventDispatcher.access$0(EventDispatcher.java:104)
org.eclipse.jdt.internal.debug.core.EventDispatcher$1.run(EventDispatcher.java:248)
org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)


Worker-225 [BLOCKED; waiting to lock org.eclipse.jdt.internal.debug.core.model.JDIThread@2fca2279]
org.eclipse.jdt.internal.debug.core.model.JDIThread.resumedByVM(JDIThread.java)
org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.resumeThreads(JDIDebugTarget.java:1322)
org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.resume(JDIDebugTarget.java:1174)
org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.resume(JDIDebugTarget.java:1147)
org.eclipse.jdt.internal.debug.core.model.JDIThread.resume(JDIThread.java:1302)
org.eclipse.jdt.internal.debug.core.model.JDIStackFrame.resume(JDIStackFrame.java:397)
org.eclipse.debug.internal.core.commands.ResumeCommand.execute(ResumeCommand.java:26)
org.eclipse.debug.internal.core.commands.ForEachCommand.doExecute(ForEachCommand.java:31)
org.eclipse.debug.core.commands.AbstractDebugCommand$1.run(AbstractDebugCommand.java:213)
org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Comment 1 Michael Rennie CLA 2013-04-19 09:25:45 EDT

*** This bug has been marked as a duplicate of bug 325426 ***