Community
Participate
Working Groups
As described e.g. in bug 179439, when an instance of Eclipse was not shut down properly (crash of Eclipse, computer crash...), Eclipse will do some sort of refreshing on next startup, which can take a long time (several minutes). While it would be nice to avoid this, there are probably scenarios where the startup delay is inevitable. For these cases, it is important to at least provide feedback to the user what is going on. At present, Eclipse just seems to hang while displaying the splash screen, which is confusing and may lead the user to believe Eclipse is hung. There should be some indication that Eclipse is refreshing its state, and that this may take a while. Preferrably, the indication should be non-modal (so startup will not be interrupted).
Possible solutions: * a special progress window instead/after the regular splash screen, indicating refresh progress or * a message inserted into the splash screen image Proposed text: "Eclipse was not shut down properly and needs to re-initialize. This may take a while..."
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
