#1001536
- Created on2013-02-22 17:32
- Reported by
- StatusFixed
- PriorityNormal (3)
- Assigned to
- Milestone
- Plan Level-
- Due Date-
Semantic Highlighting Job should be canceled by the plugin that scheduled them during shutdown
The following warning is queued in the Error Log view if Eclipse is shutted down while the Semantic Highlighting Job is running:
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: scala.tools.eclipse.semantichighlighting.Presenter$SemanticHighlightingJob
Stray Semantic Highlighting jobs (that appear to be running) prevent new jobs to be scheduled, leading to editors that have no semantic highlighting. This bad state can be triggered by changing the file while semantic highlighting is running.
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: scala.tools.eclipse.semantichighlighting.Presenter$SemanticHighlightingJob
Stray Semantic Highlighting jobs (that appear to be running) prevent new jobs to be scheduled, leading to editors that have no semantic highlighting. This bad state can be triggered by changing the file while semantic highlighting is running.
Leave a comment
on 2013-03-08 16:38 *
By Iulian Dragos
Description changed from The following warning is qu... to The following warning is qu...
on 2013-06-05 14:26 *
By Iulian Dragos
Assigned to set to Iulian Dragos
Status changed from New to Fixed
(In scala-ide:5e511529b0565dd27448a5bc07877d0120ddf679) Return `OK_STATUS` from the semantic highlighting job when the editor is dirty.
Previously, we announced that the job finishes asynchronously (`ASYNC_FINISH`),
but forgot to call `done` if the editor was dirty (and no UI asyncExec was
performed at all). This lead in turn to the job manager thinking that the job
is still running and not scheduling another run, ever, meaning the loss of
semantic highlighting.
Fixed #1001536.
Branch: platform/juno
Previously, we announced that the job finishes asynchronously (`ASYNC_FINISH`),
but forgot to call `done` if the editor was dirty (and no UI asyncExec was
performed at all). This lead in turn to the job manager thinking that the job
is still running and not scheduling another run, ever, meaning the loss of
semantic highlighting.
Fixed #1001536.
Branch: platform/juno