Community
Participate
Working Groups
Executing test cases produce a NPE in delta processor when using JDT/core version v_353. The NPE is: java.lang.NullPointerException at org.eclipse.jdt.internal.core.DeltaProcessor.resourceChanged (DeltaProcessor.java(Compiled Code)) at org.eclipse.core.internal.events.NotificationManager$1.run (NotificationManager.java(Compiled Code)) at org.eclipse.core.internal.runtime.InternalPlatform.run (InternalPlatform.java(Compiled Code)) at org.eclipse.core.internal.events.NotificationManager.notify (NotificationManager.java(Compiled Code)) at org.eclipse.core.internal.events.NotificationManager.notify (NotificationManager.java(Compiled Code)) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges (NotificationManager.java(Compiled Code)) at org.eclipse.core.internal.resources.Workspace.broadcastChanges (Workspace.java(Compiled Code)) at org.eclipse.core.internal.resources.Workspace.endOperation (Workspace.java(Compiled Code)) at org.eclipse.core.internal.resources.Resource.delete(Resource.java (Compiled Code)) at org.eclipse.core.internal.resources.Resource.delete (Resource.java:678) at org.eclipse.jdt.ui.tests.reorg.CopyToClipboardActionTest.delete (CopyToClipboardActionTest.java:166) at org.eclipse.jdt.ui.tests.reorg.CopyToClipboardActionTest.tearDown (CopyToClipboardActionTest.java:133) at junit.framework.TestCase.runBare(TestCase.java(Compiled Code)) at junit.framework.TestCase.run(TestCase.java(Compiled Code)) at junit.framework.TestCase.run(TestCase.java(Compiled Code)) at junit.framework.TestCase.run(TestCase.java(Compiled Code)) at junit.framework.TestCase.run(TestCase.java(Compiled Code)) at junit.framework.TestSuite.run(TestSuite.java(Compiled Code)) at junit.framework.TestSuite.run(TestSuite.java(Compiled Code)) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.framework.TestResult.runProtected(TestResult.java(Compiled Code)) at junit.extensions.TestSetup.run(TestSetup.java:23) at junit.framework.TestSuite.run(TestSuite.java(Compiled Code)) at junit.framework.TestSuite.runTest(TestSuite.java(Compiled Code)) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests (RemoteTestRunner.java:393) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run (RemoteTestRunner.java:277) at org.eclipse.pde.internal.junit.ui.RemotePluginTestRunner.main (RemotePluginTestRunner.java:30) at org.eclipse.pde.internal.junit.ui.UITestApplication.runEventLoop (UITestApplication.java:35) at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385) at org.eclipse.core.internal.boot.InternalBootLoader.run (InternalBootLoader.java:845) at org.eclipse.core.boot.BootLoader.run(BootLoader.java:431) at EclipseRuntimeLauncher.main(EclipseRuntimeLauncher.java:24)
performing a dummy search before deleting the file fixes the test problem
This code hasn't changed in a long time. Something else must have changed elsewhere. Can you obtain the line number in the stack trace ?
Cannot be reproduce when using IBM JRE>SR3 or other VM vendor. Also can't be reproduced when turning JIT off. Would close as VM bug.
Closing as VM bug
I rerun the test using SC SR5 and we still get the NPE, although without line numbers. I will retry with -XDebug -XJ9
It passes when using the following VM args: -Xdebug -Xj9 -Xprod. So this seems to be a problem of the IBM VM.
This is the mode I had tested when claiming >SR3. I still believe this is a VM JIT bug.
