Community
Participate
Working Groups
Build: N20050504 I recently added instrumentation to log the case where jobs are still running after the runtime has finished shutdown. From my log, I see such a case is happening in this build: !ENTRY org.eclipse.core.runtime 2 2 2005-05-03 17:40:54.861 !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.jdt.internal.core.search.processing.JobManager$1$ProgressJob Note that after org.eclipse.jdt.core has shutdown, it will not be possible to load classes from that plugin. Therefore you should cancel all jobs that you created during your shutdown, and possibly also join() them if they are not very responsive to cancelation.
I believe we already do so. Somehow something must be getting wrong.
Actually we didn't not join. John must have seen a job just before it finished (at worse it would run for 500ms). Changed JobManager to cancel and join on the progress job on shutdown.
Verified in i20050527-0010