Community
Participate
Working Groups
The spash screen gets currently updated very frequently with message about "Loading xyz ..." These messages are to fast to read and I suggest to replace them with a static message "Loading"...
With current progress reporting: Millisencs 1875 Millisencs 1940 Millisencs 1893 Millisencs 1795 Millisencs 1658 Millisencs 1791 Without bundle information Milli 1896 Milli 1715 Milli 1770 Milli 1700 Milli 1937 Milli 1701 Without bundle info and only every 4 ticks a UI update Milli 1605 Milli 1640 Milli 1587 Milli 1760 Milli 1721 Milli 1618
To test the change: Add the following to line 649 in Workbench.java showProgress = true; long start = System.currentTimeMillis(); Add the following before if (returnCode[0] == PlatformUI.RETURN_OK) { in line 675 long stop = System.currentTimeMillis(); System.out.println("Milli " + (stop - start)); //$NON-NLS-1$
New Gerrit change created: https://git.eclipse.org/r/76912
It also could lead to misinterpreting startup performance issues. On my Windows 7 machine at work the startup process hangs after starting the PC new with saying "Loading org.eclipse.equinox.frameworkadmin" Note that this is only happening the first time I start Eclipse Neon after the PC is started. On restarting it doesn't happen anymore. It sometimes comes if I switch to another workspace. But even that is not reproducable everytime. I suspect this is more related to cold start and Java in general and not Eclipse, as sub-sequent starts of Eclipse Neon are quite fast. But the message tells the user that there is a loading issue with the platform.
-1 on removing the messages, at least by default: they provide valuable debugging support for diagnosing startup problems.
I've never found the messages to be very helpful in debugging. Seems to me it is often the bundle *after* the one displayed that has a problem, and there is no way to determine which one that is without some other debugging. I do like the "progress" though. Seems to me it ought to be "percent" or perhaps something like "n of total" displayed (which could be in increments of 10 or something, if that improved performance). Naturally "total" may not be known exactly the first time, and we would just have to include an initial guess. But then each time it's started, "total" could be updated and "remembered" in instance preferences so it would be more accurate over time. The advantage of this is that there would then be sort of an "explanation" presented to the user that the more they install, the longer the startup is (typically). Just an idea.
And, I meant to say, I think some work was done similar to this, like 6 years ago. But, I looked and could not find any bugs that mentioned it. I looked primarily in 'releng' though, no "UI".
*** This bug has been marked as a duplicate of bug 445802 ***
