Community
Participate
Working Groups
Build Identifier: I20110613-1736 No matter the version, Eclipse displays a large error log each time an attempt to open it occurs. First it stores a 1MB large (11000+ lines) log file in the configuration folder. Then, on every subsequent attempt, it displays the same log file details, a smaller file (12KB) each time. All attempts to alter .ini or .config file have failed to get it to start. Reproducible: Always Steps to Reproduce: 1. Download Eclipse 2. Unzip/Untar 3. Double Click application icon to run program
Created attachment 200401 [details] a screen shot of what pops up instead of eclipse running
Created attachment 200402 [details] the details of the general, smaller log file
It is possible that the install is corrupted, Sometimes StuffIt fails to extract the archive properly. Try BOMArchiveHelper or try extracting it from the command line (see bug 131650) tar -xzf eclipse-SDK-3.7-macosx-cocoa.tar.gz
I will try extracting using cmd line, and reply here of the results asap (I apologize that it may take a few days to report back, as my computer is being serviced right now for a broken screen) (In reply to comment #3) > It is possible that the install is corrupted, Sometimes StuffIt fails to > extract the archive properly. > > Try BOMArchiveHelper or try extracting it from the command line (see bug > 131650) > tar -xzf eclipse-SDK-3.7-macosx-cocoa.tar.gz
Hey all, I tried extracting using the terminal (tar -xzf) as suggested - but I still cannot open eclipse, getting the same very very large log file, and then subsequent log files as posted above. Any other ideas? (In reply to comment #4) > I will try extracting using cmd line, and reply here of the results asap > (I apologize that it may take a few days to report back, as my computer is > being serviced right now for a broken screen) > > (In reply to comment #3) > > It is possible that the install is corrupted, Sometimes StuffIt fails to > > extract the archive properly. > > > > Try BOMArchiveHelper or try extracting it from the command line (see bug > > 131650) > > tar -xzf eclipse-SDK-3.7-macosx-cocoa.tar.gz
Attach the bigger log file to this bug. And please verify the checksum of your download.
Created attachment 200865 [details] first large log file
Created attachment 200866 [details] first large log file, continued the first log file is over 11,000 lines and 1MB, and continues into this smaller file
I verified that my checksum was correct, even trashed the install, then re-downloaded, 3 times, and checked each... I attached the huge log file that is created on the first attempt to open eclipse (2 log files are created in the configurations folder, with the 2nd being a continuation of the first) I'm sorry I didn't include this file initially - since it is over 11,000 lines long and I figured the smaller log files that were created on each subsequent attempt to run eclipse would be enough (easier to run through than so many lines) (In reply to comment #6) > Attach the bigger log file to this bug. And please verify the checksum of your > download.
I'd try reinstalling your Java runtime(s) if I were you. Also see bug 301815 and bug 318046.
I reinstalled Java Version 1.6.0_26 and tried, but nothing. Then I followed "bug 318046" and found a user (22nd comment) who suggested renaming the "Extensions" folder in HD/Library/Java/ to something new (like, say, Extensions_old). Somehow this worked - eclipse runs!! BUT, there is an issue with the Extensions folder that affects how it runs (should I open a new bug report for this new find?? I feel it's highly related, considering the way in which we found this solution, so I'll continue here...) - One should be able to have Extensions - I added .jar extensions to use for projects that require them (such as jfreechart or junit) After renaming the folder, if I revert to the old name "Extensions" (so it can be used properly) then eclipse still now runs, but opens with this error in the sidebar: Could not create the view: Plug-in "org.eclipse.jdt.ui" was unable to instantiate class "org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart". java.lang.NullPointerException at org.eclipse.jface.dialogs.DialogSettings.load(DialogSettings.java:300) at org.eclipse.jface.dialogs.DialogSettings.load(DialogSettings.java:328) at org.eclipse.jface.dialogs.DialogSettings.load(DialogSettings.java:269) at org.eclipse.jface.dialogs.DialogSettings.load(DialogSettings.java:286) at org.eclipse.ui.plugin.AbstractUIPlugin.loadDialogSettings(AbstractUIPlugin.java:411) at org.eclipse.ui.plugin.AbstractUIPlugin.getDialogSettings(AbstractUIPlugin.java:232) at org.eclipse.jdt.internal.ui.JavaPlugin.getDialogSettingsSection(JavaPlugin.java:1046) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart.<init>(PackageExplorerPart.java:354) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184) at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:268) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:264) at org.eclipse.ui.internal.registry.ViewDescriptor.createView(ViewDescriptor.java:63) at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:327) at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:229) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.WorkbenchPage$ActivationList.setActive(WorkbenchPage.java:4317) at org.eclipse.ui.internal.WorkbenchPage$18.runWithException(WorkbenchPage.java:3359) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3935) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3612) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803) at org.eclipse.ui.internal.Workbench$33.runWithException(Workbench.java:1595) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3935) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3612) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) As well, one cannot "Install New Software" as it says the install has not been configured properly. (And of course - Thanks for all the help with the initial issue!) (In reply to comment #10) > I'd try reinstalling your Java runtime(s) if I were you. Also see bug 301815 > and bug 318046.
(In reply to comment #11) > After renaming the folder, if I revert to the old name "Extensions" (so it can > be used properly) then eclipse still now runs, but opens with this error Are you using a new workspace? Please start Eclipse and point it at a non-existent folder so it generates a new workspace.
yes - there was no "workspace" folder in Documents Then I opened Eclipse and directed it to generate a new folder called "workspace" and work from there So it created this new folder on start up (In reply to comment #12) > (In reply to comment #11) > > After renaming the folder, if I revert to the old name "Extensions" (so it can > > be used properly) then eclipse still now runs, but opens with this error > > Are you using a new workspace? Please start Eclipse and point it at a > non-existent folder so it generates a new workspace.
The JRE extensions directory is the scourge of the Earth, a feature that should have never been implemented by Sun. It's a breeding ground for subtle and difficult-to-track-down bugs relating to JAR dependencies. Each Java app should define it's own runtime classpath, not rely on some third-party junk stuffed into a location that ALL java apps will inherit. I suggest we close this bug, as was done for bug 301815 and bug 318046, and open a new one to add this to the downloads page and/or troubleshooting guides.
(In reply to comment #14) > The JRE extensions directory is the scourge of the Earth, a feature that should > have never been implemented by Sun. It's a breeding ground for subtle and > difficult-to-track-down bugs relating to JAR dependencies. > Each Java app should define it's own runtime classpath, not rely on some > third-party junk stuffed into a location that ALL java apps will inherit. > I suggest we close this bug, as was done for bug 301815 and bug 318046, and > open a new one to add this to the downloads page and/or troubleshooting guides. Ok - I agree as the initial problem has now been solved. And it'd definitely be useful in troubleshooting for people who encounter this when installing. As for the errors / "unable to install new software when starting up with the Extensions folder intact" as mentioned in Comment 11 - I'm still new to using this forum/bug reporting, so if someone can file a new report in the right "product"/"component" section with the info from "Comment 11" that'd be cool. And again, thanks for the time you guys took to help find a solution to this bug report.
I opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=354564 for the issue described in comment #11 but I would not expect any miracle there. I think putting back Extensions in place is likely to be the root cause of the issues you are running into and you are likely to run in more.
(In reply to comment #16) > I opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=354564 for the issue > described in comment #11 but I would not expect any miracle there. I think > putting back Extensions in place is likely to be the root cause of the issues > you are running into and you are likely to run in more. thanks for the new bug report (i'm new, so wasn't sure how to close this one) i'll go there for this new issue -- and if anyone has authority to edit troubleshooting guides for new users, i'd definitely add this report to the list for people to check their extensions folder
