Community
Participate
Working Groups
After we have fixed various "auto-build on startup" issues I see that on startup a LOT of "Activating working set updaters for bundle ..." jobs are running and keep UI busy for some time. I've counted them and I had ~ 40 UI jobs! Looking on the code in org.eclipse.ui.internal.AbstractWorkingSetManager.bundleChanged(BundleEvent) one can see that *for every bundle activation event* an UI job is triggered on startup, *independently* if the job at the end just does nothing in UI (they just reading some registry data etc and terminate). The scary thing is, from 40 UI jobs only ONE was actually doing something useful! The rest is really wasting UI time on startup. I will push a patch in a moment.
New Gerrit change created: https://git.eclipse.org/r/127057
Gerrit change https://git.eclipse.org/r/127057 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?id=aa09a7650570a150755db6723a3ec12975086255