GPE debug error: ContentViewer must have a content provider when input is set

480 views
Skip to first unread message

Jeff Chimene

unread,
Nov 18, 2009, 4:52:55 PM11/18/09
to GWT-users-list
I received this error today after starting a debug session: "ContentViewer must have a content provider when input is set"

I resisted writing this email, so did not copy more details.

Restarting Eclipse did not resolve this error. I resolved this problem by closing/opening the project.

I really don't know how to reproduce it. If it happens again, i will post the entire error log.

Google Plugin for Eclipse 3.5    1.1.101.v200911161426    com.google.gdt.eclipse.suite.e35.feature.feature.group 
Eclipse Web Developer Tools    3.1.1.v200908120400-7R77FSpEVw2xXR0CtKvX6bG6a2qU    org.eclipse.wst.web_ui.feature.feature.group

Rajeev Dayal

unread,
Nov 18, 2009, 5:12:42 PM11/18/09
to google-we...@googlegroups.com
Hi Jeff,

This is a known bug that we'll have fixed for the next RC.

To avoid this error, do not close the Web App Launch View once it has been opened (minimization is okay, the problem occurs when you actually close the view). If you do get into this state, restarting Eclipse will fix the problem. 

Sorry about this - I know it is an annoying bug.


Rajeev

--

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=.

Jeff Chimene

unread,
Nov 18, 2009, 5:43:22 PM11/18/09
to google-we...@googlegroups.com
On Wed, Nov 18, 2009 at 3:12 PM, Rajeev Dayal <rda...@google.com> wrote:
Hi Jeff,

This is a known bug that we'll have fixed for the next RC.

To avoid this error, do not close the Web App Launch View once it has been opened (minimization is okay, the problem occurs when you actually close the view).

Hi Rajeev,

That's probably the case. I do seem to recall closing the view, rather than minimizing same. The new view is extremely cool, btw.
 
If you do get into this state, restarting Eclipse will fix the problem. 

I did cycle Eclipse, but it didn't resolve the issue. I normally exit Eclipse w/ one or more projects open.

The "last gasp" was to close/reopen the project. That did seem to be the cure.

I was quite surprised that cycling Eclipse didn't clear "whatever". That's why I resisted a post: I figured it was pilot error.
I even checked ps -ax to be sure, for sure. 

If you have the fix, great. Just saying that closing/reopening the project was the only way to reset the state. Such action seems to force Eclipse into some kind of state rebuild?

Congrats on the GPE: muy suave.


Rajeev Dayal

unread,
Nov 25, 2009, 10:36:01 AM11/25/09
to google-we...@googlegroups.com
Hey Jeff,

Sorry it took me a while to get back to you.

On Wed, Nov 18, 2009 at 5:43 PM, Jeff Chimene <jchi...@gmail.com> wrote:


On Wed, Nov 18, 2009 at 3:12 PM, Rajeev Dayal <rda...@google.com> wrote:
Hi Jeff,

This is a known bug that we'll have fixed for the next RC.

To avoid this error, do not close the Web App Launch View once it has been opened (minimization is okay, the problem occurs when you actually close the view).

Hi Rajeev,

That's probably the case. I do seem to recall closing the view, rather than minimizing same. The new view is extremely cool, btw.

Glad that you're finding it helpful :).
 
 
If you do get into this state, restarting Eclipse will fix the problem. 

I did cycle Eclipse, but it didn't resolve the issue. I normally exit Eclipse w/ one or more projects open.

That is definitely odd. Tell me, after you cycled Eclipse, did you ever close the Web App Launch View, or once you restarted Eclipse, did you just open the view and experience this problem?

Jeff Chimene

unread,
Nov 26, 2009, 11:30:26 AM11/26/09
to google-we...@googlegroups.com
On 11/25/2009 08:36 AM, Rajeev Dayal wrote:
> Hey Jeff,
>
> Sorry it took me a while to get back to you.
>
> On Wed, Nov 18, 2009 at 5:43 PM, Jeff Chimene <jchi...@gmail.com
> <mailto:jchi...@gmail.com>> wrote:
>
>
>
> On Wed, Nov 18, 2009 at 3:12 PM, Rajeev Dayal <rda...@google.com
> <mailto:rda...@google.com>> wrote:
>
> Hi Jeff,
>
> This is a known bug that we'll have fixed for the next RC.
>
> To avoid this error, do not close the Web App Launch View once
> it has been opened (minimization is okay, the problem occurs
> when you actually close the view).
>
>
> Hi Rajeev,
>
> That's probably the case. I do seem to recall closing the view,
> rather than minimizing same. The new view is extremely cool, btw.
>
>
> Glad that you're finding it helpful :).
>
>
> If you do get into this state, restarting Eclipse will fix the
> problem.
>
>
> I did cycle Eclipse, but it didn't resolve the issue. I normally
> exit Eclipse w/ one or more projects open.
>
>
> That is definitely odd. Tell me, after you cycled Eclipse, did you ever
> close the Web App Launch View, or once you restarted Eclipse, did you
> just open the view and experience this problem?

I cannot remember. To be sure, are we talking about the view that has an
icon that is a blue globe containing a stylized "g"? I see in RC2 it's
now called "Development Mode". If that's the view, I open it via the
"Debug" perspective. Rarely, if ever, do I explicitly open the view. In
RC1 & RC2, I try to minimize, rather than close it.

FWIW, this failure hasn't occurred again.

I sometimes use Eclipse in an X environment where the server and client
are different machines. It may be that the subject of this thread was a
result of such a switch. I have noticed that Eclipse sometimes fails to
start correctly after switching X servers. In such cases, Eclipse fails
when opening one or more Editor Views. The error message is displayed
using the Eclipse "details" error widget. The message associated with
this thread wasn't displayed using that error widget. I'll capture the
associated message and post to this thread when next Eclipse fails to
open an Editor View.

Jeff Chimene

unread,
Nov 26, 2009, 10:29:50 PM11/26/09
to google-we...@googlegroups.com
Hi Rajeev

Here's a log from an Eclipse crash this evening. This occurs during startup. It's usually cured by closing and reopening the project.

org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNotFoundException: An error occurred while automatically activating bundle com.google.gwt.eclipse.core (511).
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:125)
    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:381)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:457)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:398)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
    at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:326)
    at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:231)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1193)
    at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:160)
    at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:874)
    at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
    at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:51)
    at org.eclipse.jdt.core.JavaCore.computeClasspathContainerInitializer(JavaCore.java:2699)
    at org.eclipse.jdt.core.JavaCore.getClasspathContainerInitializer(JavaCore.java:2675)
    at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2589)
    at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1778)
    at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:2652)
    at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2578)
    at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2679)
    at org.eclipse.jdt.internal.core.ClasspathChange.generateDelta(ClasspathChange.java:218)
    at org.eclipse.jdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:1916)
    at org.eclipse.jdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:470)
    at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:291)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
    at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:186)
    at org.eclipse.core.internal.resources.SavedState.processResourceChangeEvents(SavedState.java:77)
    at org.eclipse.jdt.internal.core.JavaModelManager$20.run(JavaModelManager.java:4623)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1782)
    at org.eclipse.jdt.internal.core.JavaModelManager$19.run(JavaModelManager.java:4615)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.osgi.framework.BundleException: The activator com.google.gwt.eclipse.core.GWTPlugin for bundle com.google.gwt.eclipse.core is invalid
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:157)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:751)
    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:408)
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111)
    ... 35 more
Caused by: java.lang.NoClassDefFoundError: com/google/gdt/eclipse/core/AbstractGooglePlugin
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:183)
    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(ClasspathManager.java:576)
    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:546)
    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:477)
    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass_LockClassLoader(ClasspathManager.java:465)
    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:445)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:211)
    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:381)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:457)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:398)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
    at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:326)
    at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:231)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:150)
    ... 40 more
Caused by: org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNotFoundException: An error occurred while automatically activating bundle com.google.gdt.eclipse.core (506).
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:125)
    ... 35 more
Caused by: org.osgi.framework.BundleException: The activator com.google.gdt.eclipse.core.CorePlugin for bundle com.google.gdt.eclipse.core is invalid
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:157)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:751)
    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:408)
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111)
    ... 35 more
Caused by: java.lang.NoClassDefFoundError: org/eclipse/jdt/ui/JavaElementImageDescriptor
    at java.lang.Class.getDeclaredConstructors0(Native Method)
    at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
    at java.lang.Class.getConstructor0(Class.java:2699)
    at java.lang.Class.newInstance0(Class.java:326)
    at java.lang.Class.newInstance(Class.java:308)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:152)
    ... 40 more
Caused by: org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNotFoundException: An error occurred while automatically activating bundle org.eclipse.jdt.ui (397).
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:125)
    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:381)
    at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:33)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:454)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:398)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
    ... 46 more
Caused by: org.osgi.framework.BundleException: The activator org.eclipse.jdt.internal.ui.JavaPlugin for bundle org.eclipse.jdt.ui is invalid
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:157)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:751)
    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:408)
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111)
    ... 56 more
Caused by: java.lang.NoClassDefFoundError: org/eclipse/ui/editors/text/templates/ContributionTemplateStore
    at java.lang.Class.getDeclaredConstructors0(Native Method)
    at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
    at java.lang.Class.getConstructor0(Class.java:2699)
    at java.lang.Class.newInstance0(Class.java:326)
    at java.lang.Class.newInstance(Class.java:308)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:152)
    ... 61 more
Caused by: org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNotFoundException: An error occurred while automatically activating bundle org.eclipse.ui.editors (199).
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:125)
    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:381)
    at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:33)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:454)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:398)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
    ... 67 more
Caused by: org.osgi.framework.BundleException: Exception in org.eclipse.ui.internal.editors.text.EditorsPlugin.start() of bundle org.eclipse.ui.editors.
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:806)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:755)
    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:408)
    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111)
    ... 77 more
Caused by: org.eclipse.swt.SWTException: Invalid thread access
    at org.eclipse.swt.SWT.error(SWT.java:3884)
    at org.eclipse.swt.SWT.error(SWT.java:3799)
    at org.eclipse.swt.SWT.error(SWT.java:3770)
    at org.eclipse.swt.widgets.Display.error(Display.java:1150)
    at org.eclipse.swt.widgets.Display.checkDevice(Display.java:712)
    at org.eclipse.swt.widgets.Display.disposeExec(Display.java:1127)
    at org.eclipse.jface.resource.ColorRegistry.hookDisplayDispose(ColorRegistry.java:268)
    at org.eclipse.jface.resource.ColorRegistry.<init>(ColorRegistry.java:123)
    at org.eclipse.jface.resource.ColorRegistry.<init>(ColorRegistry.java:106)
    at org.eclipse.ui.internal.themes.WorkbenchThemeManager.<init>(WorkbenchThemeManager.java:98)
    at org.eclipse.ui.internal.themes.WorkbenchThemeManager.getInstance(WorkbenchThemeManager.java:58)
    at org.eclipse.ui.internal.Workbench.getThemeManager(Workbench.java:3153)
    at org.eclipse.ui.internal.editors.text.EditorsPlugin.start(EditorsPlugin.java:213)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:783)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:774)
    ... 82 more


Jeff Chimene

unread,
Nov 26, 2009, 10:33:33 PM11/26/09
to google-we...@googlegroups.com
On Thu, Nov 26, 2009 at 8:29 PM, Jeff Chimene <jchi...@gmail.com> wrote:
Hi Rajeev

Here's a log from an Eclipse crash this evening. This occurs during startup. It's usually cured by closing and reopening the project.

Nope. I had to exit Eclipse to fix this error.  The Project Explorer view wouldn't open.

Rajeev Dayal

unread,
Nov 30, 2009, 11:56:23 AM11/30/09
to google-we...@googlegroups.com
Hey Jeff,

Thanks for reporting this. I've done some investigation, and it seems that this problem is happening because one of our plugins accesses the class JavaElementImageDescriptor, which then causes the activation of some UI-related plugins. That results in a SWT exception, because the initialization is happening on a non-UI thread.

At this point, I'm not sure if this is an issue with Eclipse or with our plugin. I'll reach out to the Eclipse guys and figure it out. I'll post back my findings on this thread.


Rajeev

--

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

Miguel Méndez

unread,
Nov 30, 2009, 12:34:07 PM11/30/09
to google-we...@googlegroups.com
The following line in the log makes me thing that JDT failed to load:

The activator org.eclipse.jdt.internal.ui.JavaPlugin for bundle org.eclipse.jdt.ui is invalid

Searching the different groups it sounds like other people have run into a similar problem with other plugins.  Here is a link to what I found: http://www.eclipse.org/forums/index.php?t=msg&goto=234102&S=1c71d503cef7c45929b35583ab8ff807.

I wonder if this is what you are seeing something similar?  Are you still in this state?  If so, could you try deleting the .metadata/.plugins/org.eclipse.jdt.core/variablesAndContainers.dat when this problem happens.  It looks like JDT fails to load if that file is corrupted.

Also, what platform are you running on?  

--

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.



--
Miguel

Jeff Chimene

unread,
Nov 30, 2009, 1:12:31 PM11/30/09
to google-we...@googlegroups.com


2009/11/30 Miguel Méndez <mme...@google.com>

The following line in the log makes me thing that JDT failed to load:

The activator org.eclipse.jdt.internal.ui.JavaPlugin for bundle org.eclipse.jdt.ui is invalid

Searching the different groups it sounds like other people have run into a similar problem with other plugins.  Here is a link to what I found: http://www.eclipse.org/forums/index.php?t=msg&goto=234102&S=1c71d503cef7c45929b35583ab8ff807.

I wonder if this is what you are seeing something similar?  

Yes, it's similar. However, from that thread it sounds like the failure happens at every Eclipse load. That's not happening to me. From what I glean, the suggested fix relates to the jdt.core version. Here is what my startup log shows:
Id: org.eclipse.jdt.core, Version: 3.5.1.v_972_R35x
Id: org.eclipse.jdt.core.manipulation, Version: 1.3.0.v20090603
Id: org.eclipse.jdt.core.manipulation.source, Version: 1.3.0.v20090603
Id: org.eclipse.jdt.core.source, Version: 3.5.1.v_972_R35x
Id: org.eclipse.jdt.core, Version: 3.5.1.v_972_R35x, Location: reference:file:plugins/org.eclipse.jdt.core_3.5.1.v_972_R35x.jar
Id: org.eclipse.jdt.core.manipulation, Version: 1.3.0.v20090603, Location: reference:file:plugins/org.eclipse.jdt.core.manipulation_1.3.0.v20090603.jar
 
Are you still in this state?

It happens "every so often". The main stimulant seems to be switching the X server to Windows from Linux and vice versa. It doesn't happen every time.
 
 If so, could you try deleting the .metadata/.plugins/org.eclipse.jdt.core/variablesAndContainers.dat when this problem happens.  

Yes. I'll try it.
 
It looks like JDT fails to load if that file is corrupted.

Also, what platform are you running on?  


The X client is always Debian Linux Testing/Unstable. The X server varies between Windows 2K, and Debian Linux Testing/Unstable. However, I don't track the Debian Eclipse package. I custom install Eclipse; which is version 3.5

Miguel Méndez

unread,
Nov 30, 2009, 1:30:25 PM11/30/09
to google-we...@googlegroups.com
Would it be possible to get your .metadata/.log file?  You can send it to me offline if you like.

--

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.



--
Miguel
Reply all
Reply to author
Forward
0 new messages