Community
Participate
Working Groups
Build ID: M20071023-1652 Steps To Reproduce: 1.Start eclipse 2. 3. More information: I see quite a lot of these errors in the log: !MESSAGE While loading class "org.eclipse.mylyn.tasks.ui.TaskListManager", thread "Thread[main,6,main]" timed out waiting (5000ms) for thread "Thread[Worker-1,5,main]" to finish starting bundle "update@plugins/org.eclipse.mylyn.tasks.ui_2.1.0.v20070927-0900.jar [86]". To avoid deadlock, thread "Thread[main,6,main]" is proceeding but "org.eclipse.mylyn.tasks.ui.TaskListManager" may not be fully initialized. !STACK 0 org.osgi.framework.BundleException: State change in progress for bundle "update@plugins/org.eclipse.mylyn.tasks.ui_2.1.0.v20070927-0900.jar" by thread "Worker-1". at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1141) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:258) at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:400) at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:417) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:189) at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:340) at org.eclipse.osgi.framework.internal.core.SingleSourcePackage.loadClass(SingleSourcePackage.java:37) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:405) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:369) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:357) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at org.eclipse.mylyn.context.ui.ContextUiPlugin$5.run(ContextUiPlugin.java:259) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3296) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2974) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) 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:508) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447) at org.eclipse.equinox.launcher.Main.run(Main.java:1173) at org.eclipse.equinox.launcher.Main.main(Main.java:1148) Caused by: org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException ... 40 more I'm reporting this basically because I have no idea whether it is related to the instability of Eclipse on my system. Additional information: The environment is Ubuntu 2.6.22-14 x86_64, java version 1.6.0_03-b05 64 bit. Eclipse itself is running with these vmargs: -XX:PermSize=512M -XX:MaxPermSize=512M -Xms512M -Xmx2048M and it has these plugins: Subclipse 1.2.4 TestNG 5.7.0.1 JettyLauncher 1.4.1 WST 2.0.1 PDT 1.0.2 (and dependencies, such as EMF, GEF, XSD, Mylyn)
Bug 188524 has more information about the Mylyn startup warnings which should not appear anymore with more recent weekly versions. *** This bug has been marked as a duplicate of bug 214092 ***
(In reply to comment #1) > *** This bug has been marked as a duplicate of bug 214092 *** Steffen, I don't think the VM crash reported by bug 214092 is related to this as Thomas only mentions his log files being filled up instead of seeing Eclipse crash.
Sorry, I just saw that the crash was on a 64-bit JVM. I didn't realize that the crashes only happen on certain JVM versions. Thomas, do you have hs_err_pid*.log files in the directory Eclipse was started from?
(In reply to comment #3) > Sorry, I just saw that the crash was on a 64-bit JVM. I didn't realize that the > crashes only happen on certain JVM versions. > > Thomas, do you have hs_err_pid*.log files in the directory Eclipse was started > from? My point was that nowhere in Thomas's comment 0 does he mention the word crash. So I don't think his Eclipse is even crashing for starters. (Quoting comment #0) > I see quite a lot of these errors in the log: > ... > I'm reporting this basically because I have no idea whether it is related to > the instability of Eclipse on my system. Hence, I think this is merely a duplicate of bug 188524. Do you see what I'm getting at?
Okay, let's start over :). The Mylyn warnings are most likely unrelated to the underlying instability problem and have been fixed in recent weekly releases. To verify that please try upgrading to the latest Mylyn weekly build: http://www.eclipse.org/mylyn/downloads/ > I'm reporting this basically because I have no idea whether it is related to the > instability of Eclipse on my system. Thomas, could you specify instability in more detail? Does Eclipse crash? Do you have hs_err_pid*.log files in the directory Eclipse was started from?
(In reply to comment #5) > Okay, let's start over :). > > The Mylyn warnings are most likely unrelated to the underlying instability > problem and have been fixed in recent weekly releases. To verify that please > try upgrading to the latest Mylyn weekly build: > > http://www.eclipse.org/mylyn/downloads/ > > > I'm reporting this basically because I have no idea whether it is related to the > > instability of Eclipse on my system. > > Thomas, could you specify instability in more detail? Does Eclipse crash? Do > you have hs_err_pid*.log files in the directory Eclipse was started from? > Eclipse does not crash (hence no hs_err_pid*.log files), but at some point becomes really unstable and runs of memory or reaches GC limits (see bug 219697). This however happens while using Eclipse, e.g. compiling classes etc. and thus to me did not seem related to this issue here. Of course I might be wrong ...
Thomas: The warnings in the description a duplicate of bug 188524 which has been resolved. It is very extremely unlikely to have caused any of the instability noted. If you have additional information on that instability we can reopen and move this bug to Platform, or you could file a new bug. *** This bug has been marked as a duplicate of bug 188524 ***
