Design stability problems

[colinzhao]

I am experiencing various stability problems with the following build

Eclipse 3.4
GWT Designer Version: 7.1.0 (build 7.1.0.2009071705239)
GWT 1.6.4 and plugin

!SESSION 2009-07-19 11:00:54.539 -----------------------------------------------
eclipse.buildId=M20090211-1700
java.version=1.6.0_07
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86

and eclipse init parameters:

-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
512M
-framework
plugins\org.eclipse.osgi_3.4.3.R34x_v20081215-1030.jar
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms256m
-Xmx1048m


I have two problems
1. eclipse has frequent out-of-memory problem
2. Eclipse hangs on one of my project at start up after I left it open over night and my laptop had an auto reboot after MS Windows updates.

Here is a few lines from the log file of the project

!ENTRY org.eclipse.core.resources 2 10035 2009-07-19 11:01:02.362
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

!ENTRY org.eclipse.osgi 2 0 2009-07-19 11:01:09.884
!MESSAGE While loading class "com.instantiations.designer.core.editor.multi.MultiPageEditor", thread "Thread[main,6,main]" timed out waiting (5000ms) for thread "Thread[Worker-0,5,main]" to finish starting bundle "reference:file:plugins\com.instantiations.designer.core_7.1.0.200907180529.jar [819]". To avoid deadlock, thread "Thread[main,6,main]" is proceeding but "com.instantiations.designer.core.editor.multi.MultiPageEditor" may not be fully initialized.
!STACK 0
org.osgi.framework.BundleException: State change in progress for bundle "reference:file:plugins\com.instantiations.designer.core_7.1.0.200907180529.jar" by thread "Worker-0".
at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1144)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:263)
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:427)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:193)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:370)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:446)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:399)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:387)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:87)
at java.lang.ClassLoader.loadClass(Unknown Source)
at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:315)
at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:227)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1274)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:160)
at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:867)

I am going to rebuild the project, which will take me a hour or so. But the stability problem really bothers me. This is a problem with Designer or my eclipse build?

Thanks.

Colin

[Eric Clayberg]

Sounds like a problem with your Eclipse configuration since you didn't mention any issues actually using GWT Designer.

[djatnieks]

It seems to me it is a problem caused by GWT Designer. This just happened to me too - I was using GWT Designer when it just hung during a copy/paste operation. Now I cannot open that eclipse project anymore ... and you can see from the error stack that eclipse cannot load part of the GWT Designer plugin.

Code: Select all

!ENTRY org.eclipse.osgi 2 0 2009-11-06 15:51:13.899
!MESSAGE While loading class "com.instantiations.designer.core.editor.UndoManager$5", thread "Thread[main,6,main]" timed out waiting (5000ms) for thread "Thread[Worker-0,5,main]" to finish starting bundle "com.instantiations.designer.core_7.2.0.200910061108 [21]". To avoid deadlock, thread "Thread[main,6,main]" is proceeding but "com.instantiations.designer.core.editor.UndoManager$5" may not be fully initialized.
!STACK 0
org.osgi.framework.BundleException: State change in progress for bundle "reference:file:plugins/com.instantiations.designer.core_7.2.0.200910061108.jar" by thread "Worker-0".
   at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1073)
   at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:278)
   at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:408)
   at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111)
   at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:449)
   at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:211)
   at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:376)
   at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:452)
   at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:405)
   at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:393)
   at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
   at java.lang.ClassLoader.loadClass(Unknown Source)
   at java.lang.ClassLoader.loadClassInternal(Unknown Source)
   at com.instantiations.designer.core.editor.UndoManager.<init>(UndoManager.java:376)
   at com.instantiations.designer.core.editor.DesignPage$2.run(DesignPage.java:92)
   at com.instantiations.designer.core.utils.execution.ExecutionUtils.runRethrow(ExecutionUtils.java:64)
   at com.instantiations.designer.core.editor.DesignPage.initialize(DesignPage.java:89)
   at com.instantiations.designer.core.editor.multi.MultiMode.create(MultiMode.java:75)
   at com.instantiations.designer.core.editor.multi.MultiPagesMode.create(MultiPagesMode.java:70)
   at com.instantiations.designer.core.editor.multi.MultiPageEditor.createPartControl(MultiPageEditor.java:59)
   at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:662)
   at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:462)
   at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
   at org.eclipse.ui.internal.EditorAreaHelper.setVisibleEditor(EditorAreaHelper.java:271)
   at org.eclipse.ui.internal.EditorManager.setVisibleEditor(EditorManager.java:1417)
   at org.eclipse.ui.internal.EditorManager$5.runWithException(EditorManager.java:942)
   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:134)
   at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3855)
   at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476)
   at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803)
   at org.eclipse.ui.internal.Workbench$28.runWithException(Workbench.java:1384)
   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:134)
   at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3855)
   at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476)
   at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2316)
   at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
   at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
   at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
   at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
   at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
   at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
   at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
   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:368)
   at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
   at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
   at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
Caused by: org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException
   ... 57 more
Root exception:
org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException
   at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1073)
   at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:278)
   at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:408)
   at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111)
   at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:449)
   at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:211)
   at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:376)
   at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:452)
   at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:405)
   at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:393)
   at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
   at java.lang.ClassLoader.loadClass(Unknown Source)
   at java.lang.ClassLoader.loadClassInternal(Unknown Source)
   at com.instantiations.designer.core.editor.UndoManager.<init>(UndoManager.java:376)
   at com.instantiations.designer.core.editor.DesignPage$2.run(DesignPage.java:92)
   at com.instantiations.designer.core.utils.execution.ExecutionUtils.runRethrow(ExecutionUtils.java:64)
   at com.instantiations.designer.core.editor.DesignPage.initialize(DesignPage.java:89)
   at com.instantiations.designer.core.editor.multi.MultiMode.create(MultiMode.java:75)
   at com.instantiations.designer.core.editor.multi.MultiPagesMode.create(MultiPagesMode.java:70)
   at com.instantiations.designer.core.editor.multi.MultiPageEditor.createPartControl(MultiPageEditor.java:59)
   at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:662)
   at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:462)
   at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
   at org.eclipse.ui.internal.EditorAreaHelper.setVisibleEditor(EditorAreaHelper.java:271)
   at org.eclipse.ui.internal.EditorManager.setVisibleEditor(EditorManager.java:1417)
   at org.eclipse.ui.internal.EditorManager$5.runWithException(EditorManager.java:942)
   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:134)
   at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3855)
   at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476)
   at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803)
   at org.eclipse.ui.internal.Workbench$28.runWithException(Workbench.java:1384)
   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:134)
   at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3855)
   at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476)
   at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2316)
   at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
   at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
   at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
   at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
   at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
   at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
   at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
   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:368)
   at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
   at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
   at org.eclipse.equinox.launcher.Main.run(Main.java:1311)



[Eric Clayberg]

It seems to me it is a problem caused by GWT Designer.

That would be very hard to say based on the description. It could also been caused by GWT, Eclipse or even IE since all of those are also active at the same time.

Now I cannot open that eclipse project anymore

What does that mean?

you can see from the error stack that eclipse cannot load part of the GWT Designer plugin.

If your Eclipse config or plugin cache is corrupt, there are a few things you can try:

1) Delete/rename the <workspace>\.metadata\.plugins\org.eclipse.ui.workbench\workbench.xml file and restart Eclipse.

2) Uninstall and re-install GWT Designer via the Update Manager.

3) Install into a new, clean Eclipse installation with a new workspace.

[djatnieks]

It seems to me it is a problem caused by GWT Designer.

That would be very hard to say based on the description. It could also been caused by GWT, Eclipse or even IE since all of those are also active at the same time.

The reason I think it was GWT Designer is a) I was using GWT Designer at the time eclipse first hung (had to kill the process) and b) trying to open that eclipse workspace still hangs and fills the log with the above messages complaining about not being able to load some piece of GWT Designer.

Now I cannot open that eclipse project anymore

What does that mean?

Sorry I should have said "workspace" instead of "project". It means eclipse just hangs and the log fills with the messages posted earlier. The process has to be killed.

you can see from the error stack that eclipse cannot load part of the GWT Designer plugin.

If your Eclipse config or plugin cache is corrupt, there are a few things you can try:

1) Delete/rename the <workspace>\.metadata\.plugins\org.eclipse.ui.workbench\workbench.xml file and restart Eclipse.

2) Uninstall and re-install GWT Designer via the Update Manager.

3) Install into a new, clean Eclipse installation with a new workspace.

I ended up creating a new workspace and project and restoring all my workspace settings.

I just tried #1 and it works in that eclipse starts and opens my workspace, but my project is gone, so it seems the same as the solution I used.

[Eric Clayberg]

The reason I think it was GWT Designer is a) I was using GWT Designer at the time eclipse first hung (had to kill the process)

The most common reason I have seen for Eclipse to actually hang (whether using GWT Designer or any other plugin) is for Eclipse to run out of memory. That could be a problem caused by GWT Designer or it could be caused by any other plugin that is active in your environment. We would need to see the VM crash log associated with the event and/or the Eclipse ".log" file showing any entries immediately prior to the crash. A reproducible test case would also be helpful as that would conclusively show whether the problem was caused by GWT Designer, by GWT itself, or by some other issue with Eclipse.

b) trying to open that eclipse workspace still hangs and fills the log with the above messages complaining about not being able to load some piece of GWT Designer.

That is an Eclipse bug. When Eclipse crashes, it will often corrupt whatever plugin was active at the time (or its cache entries associated with that plugin). This has been a problem with Eclipse for many years which should simply not occur.

Sorry I should have said "workspace" instead of "project". It means eclipse just hangs and the log fills with the messages posted earlier. The process has to be killed.

Deleting/renaming the <workspace>\.metadata\.plugins\org.eclipse.ui.workbench\workbench.xml file and restarting Eclipse will often fix that as it has the effect of closing any open editors that would have triggered immediate start up of the affected plugins.

I ended up creating a new workspace and project and restoring all my workspace settings.
I just tried #1 and it works in that eclipse starts and opens my workspace, but my project is gone, so it seems the same as the solution I used.

None of the suggestions I made earlier would affect the existence of any of your projects. They would all still be on disk and could be easily reloaded into any (new) workspace.