Community
Participate
Working Groups
Build RC2 As shown in bug 33998, the reconciler thread is still running even after the JDT/UI plugin shutdown() has exited. It should wait for all reconciler threads to terminate before proceeding. See also bug 34069.
Moving to JDT Text. This behaviour was in since 1.0. So what are the symptoms of this problem? I don't think we should do such a change now unless there is a real problem.
There are currently no symptoms since bug 33998 was fixed to workaround the problem. In bug 34069 John Arthorne suggested that this could cause other grief.
Most runtime plugin API will throw assertion failures if you invoke methods after the runtime plugin has been shutdown. The resources plugin API will fail in similar ways since we null our reference to the workspace during shutdown of the resources plugin. There could be other side-effects of plugins shutting down out of order. I agree this probably doesn't need to be addresed for 2.1 since there is a code work-around for the only known failure case. You might want to revisit this for 2.2 though.
*** Bug 58245 has been marked as a duplicate of this bug. ***
Deferring.
Resetting priority to P3. Will be reassessed for the next release.
The problem is that waiting for the thread while closing the editor has drawbacks: - making editor closing slower for the user even though this is not necessary assuming the reconciler silently dies in the background. - can introducing deadlocks (see also bug 58245 comment 8) There are currently no plans to address this for 3.2 but I've protected against the NPE reported by bug 58245.
*** Bug 79351 has been marked as a duplicate of this bug. ***
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. If you have further information on the current state of the bug, please add it. 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.
