Console does not need to start UI job every second #2427
Merged
+11
−18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to update console status line, ProcessConsole.computeName() calls resetName() every second once console is created. This causes new UI job to be started every second via timerExec(), with code already being executed on UI thread. It is a misuse of Jobs framework, it makes use of jobs dispatching where no jobs are needed. The code can use Display.execute() for a more lightweight console status update.
As a nice side effect no jobs are flashing in the Progress view every second (if system jobs are shown).