Eclipse Community Forums: Eclipse Platform » Eclipse bug ? JVM does not die after exiting Eclipse

Home » Eclipse Projects » Eclipse Platform » Eclipse bug ? JVM does not die after exiting Eclipse

Eclipse bug ? JVM does not die after exiting Eclipse [message #262712]

Tue, 20 July 2004 15:40

Eclipse User

Originally posted by: oleg.configurecode.com

I am working on a plugin that uses Display.asyncExec in a few places to
run a thread that updates a UI widget. I am suspecting that a bug in my
code may be causing JVM not to exit in some cases. I have to force-kill
the process.

Is my suspicion correct or is it a known Eclipse bug ?

Oleg

Re: Eclipse bug ? JVM does not die after exiting Eclipse [message #262715 is a reply to message #262712]

Tue, 20 July 2004 15:43

Eclipse User

Originally posted by: oleg.configurecode.com

BTW, the error I am getting is this:

"Exception processing async thread queue
Exception processing async thread queue
java.lang.NullPointerException
org.eclipse.jdt.internal.debug.eval.ast.engine.ASTInstructio nCompiler.containsALocalType(ASTInstructionCompiler.java:331 )
org.eclipse.jdt.internal.debug.eval.ast.engine.ASTInstructio nCompiler.visit(ASTInstructionCompiler.java:2075)
org.eclipse.jdt.core.dom.MethodInvocation.accept0(MethodInvo cation.java:234)
org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2454)
org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:25 01)
org.eclipse.jdt.core.dom.ReturnStatement.accept0(ReturnState ment.java:133)
org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2454)
org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java :2524)
org.eclipse.jdt.core.dom.Block.accept0(Block.java:133)
org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2454)
org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:25 01)
org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDec laration.java:499)
org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2454)
org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java :2524)
org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclara tion.java:474)
org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2454)
org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java :2524)
org.eclipse.jdt.core.dom.CompilationUnit.accept0(Compilation Unit.java:290)
org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2454)
org.eclipse.jdt.internal.debug.eval.ast.engine.ASTEvaluation Engine.createExpressionFromAST(ASTEvaluationEngine.java:251)
org.eclipse.jdt.internal.debug.eval.ast.engine.ASTEvaluation Engine.getCompiledExpression(ASTEvaluationEngine.java:156)
org.eclipse.jdt.internal.debug.eval.ast.engine.ASTEvaluation Engine.evaluate(ASTEvaluationEngine.java:73)
org.eclipse.jdt.internal.debug.ui.JavaWatchExpressionDelegat e$EvaluationRunnable.run(JavaWatchExpressionDelegate.java:14 4)
org.eclipse.jdt.internal.debug.core.model.JDIThread$ThreadJo b.run(JDIThread.java:2510)
org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)"

Oleg wrote:

> I am working on a plugin that uses Display.asyncExec in a few places to
> run a thread that updates a UI widget. I am suspecting that a bug in my
> code may be causing JVM not to exit in some cases. I have to force-kill
> the process.
>
> Is my suspicion correct or is it a known Eclipse bug ?
>
> Oleg

Re: Eclipse bug ? JVM does not die after exiting Eclipse [message #262732 is a reply to message #262715]

Tue, 20 July 2004 16:11

Eclipse User

Originally posted by: olivier_thomannNO.ca.ibm.comSPAM

Le Tue, 20 Jul 2004 15:43:52 -0400, Oleg <oleg@configurecode.com> a
écrit :
>"Exception processing async thread queue
> Exception processing async thread queue
>java.lang.NullPointerException
> org.eclipse.jdt.internal.debug.eval.ast.engine.ASTInstructio nCompiler.containsALocalType(ASTInstructionCompiler.java:331 )
> org.eclipse.jdt.internal.debug.eval.ast.engine.ASTInstructio nCompiler.visit(ASTInstructionCompiler.java:2075)
> org.eclipse.jdt.core.dom.MethodInvocation.accept0(MethodInvo cation.java:234)
>org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2454)
Open a bug report with reproducable steps against JDT/Debug.
--
Olivier

Previous Topic:	"%key" strings not resolved on branded platform
Next Topic:	problem finding classes at runtime

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 05 22:56:00 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter