When I started up my Eclipse recently it got as far as seeming to load properly and then hanging, displaying an incredibly helpful blank error pop-up.
Sifting through message board advice for something that seemed likely to have the least chance of unintended consequences I found this:
I ran into a problem where the Eclipse just hangs and shows a blank screen on start up. On analysis I found that its due to the perspective that its trying to open with. I could not find the problem thats causing this but I wanted to open the project and do some work on the java code base.
Since I cannot change the perspective from the eclipse workbench I looked around and found the file that can be edited to make eclipse open in the perspective you want.
It is workbench.xml file that will be under %workspace%\.metadata\.plugins\org.eclipse.ui.workbench folder. Search for perspectives element and modify it to open up in the perspective you want. For e.g. to open in java perspective you can use the following
<perspectives activePart=”org.eclipse.jdt.ui.PackageExplorer” activePerspective=”org.eclipse.jdt.ui.JavaPerspective”>
The corresponding line in my workbench.xml file was <perspectives activePart=”org.eclipse.ui.console.ConsoleView” activePerspective=”org.eclipse.jdt.ui.JavaPerspective”> which, when replaced, allowed Eclipse to come to life once again.
On a tangent, it seems like a decent portion of the solutions that work don’t work for the reasons they should. Like in the above, our activePerspective attributes were the same. The problem instead was that our activePart attributes were different. So of course that leaves me wondering if others solutions out there that target fixing the perspective actually work because they coincidentally effect the real source of the problem. And how many solutions in the world are just a fallacy of cause and effect? Can’t help but wonder…