Eclipse Community Forums: TMF (Xtext) » NullPointerException in DefaultResourceDescriptionManager

Home

Home » Modeling » TMF (Xtext) » NullPointerException in DefaultResourceDescriptionManager

NullPointerException in DefaultResourceDescriptionManager [message #637283]

Thu, 04 November 2010 16:09

Eclipse User

Hi,

in one of our Xtext editors we keep seeing an NPE on the console. It seems like everything is working, but probably we shouldn't really be seeing this. It looks like the Guice injection of descriptionUtils is not happening...
Any ideas? Might this be some sort of Xtext bug?

java.lang.NullPointerException
at org.eclipse.xtext.resource.impl.DefaultResourceDescriptionMa nager.isAffected(DefaultResourceDescriptionManager.java:112)
at org.eclipse.xtext.builder.builderState.ResourceDescriptionsU pdater.findAffectedResourceDescriptions(ResourceDescriptions Updater.java:189)
at org.eclipse.xtext.builder.builderState.ResourceDescriptionsU pdater.transitiveUpdate(ResourceDescriptionsUpdater.java:91)
at org.eclipse.xtext.builder.builderState.AbstractBuilderState. transitiveUpdate(AbstractBuilderState.java:158)
at org.eclipse.xtext.builder.builderState.PersistableResourceDe scriptionsImpl.doUpdate(PersistableResourceDescriptionsImpl. java:48)
at org.eclipse.xtext.builder.builderState.PersistableResourceDe scriptionsImpl.doUpdate(PersistableResourceDescriptionsImpl. java:1)
at org.eclipse.xtext.builder.builderState.AbstractBuilderState. update(AbstractBuilderState.java:108)
at org.eclipse.xtext.builder.impl.XtextBuilder.doBuild(XtextBui lder.java:151)
at org.eclipse.xtext.builder.impl.XtextBuilder.incrementalBuild (XtextBuilder.java:135)
at org.eclipse.xtext.builder.impl.XtextBuilder.build(XtextBuild er.java:84)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildMan ager.java:629)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:172)
at org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:203)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:255)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:258)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop (BuildManager.java:311)
at org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:343)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBu ildJob.java:144)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJ ob.java:242)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Re: NullPointerException in DefaultResourceDescriptionManager [message #637421 is a reply to message #637283]

Fri, 05 November 2010 08:28

Eclipse User

Hi Mirko,

this looks like a bug. Would you please be so kind and file a ticket
with a reproducable sample attached?

Thanks a lot,
Sebastian
--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com

Am 04.11.10 21:09, schrieb Mirko Raner:
> Hi,
>
> in one of our Xtext editors we keep seeing an NPE on the console. It
> seems like everything is working, but probably we shouldn't really be
> seeing this. It looks like the Guice injection of descriptionUtils is
> not happening...
> Any ideas? Might this be some sort of Xtext bug?
>
> java.lang.NullPointerException
> at org.eclipse.xtext.resource.impl.DefaultResourceDescriptionMa
> nager.isAffected(DefaultResourceDescriptionManager.java:112)
> at org.eclipse.xtext.builder.builderState.ResourceDescriptionsU
> pdater.findAffectedResourceDescriptions(ResourceDescriptions
> Updater.java:189)
> at org.eclipse.xtext.builder.builderState.ResourceDescriptionsU
> pdater.transitiveUpdate(ResourceDescriptionsUpdater.java:91)
> at org.eclipse.xtext.builder.builderState.AbstractBuilderState.
> transitiveUpdate(AbstractBuilderState.java:158)
> at org.eclipse.xtext.builder.builderState.PersistableResourceDe
> scriptionsImpl.doUpdate(PersistableResourceDescriptionsImpl. java:48)
> at org.eclipse.xtext.builder.builderState.PersistableResourceDe
> scriptionsImpl.doUpdate(PersistableResourceDescriptionsImpl. java:1)
> at org.eclipse.xtext.builder.builderState.AbstractBuilderState.
> update(AbstractBuilderState.java:108)
> at org.eclipse.xtext.builder.impl.XtextBuilder.doBuild(XtextBui
> lder.java:151)
> at org.eclipse.xtext.builder.impl.XtextBuilder.incrementalBuild
> (XtextBuilder.java:135)
> at org.eclipse.xtext.builder.impl.XtextBuilder.build(XtextBuild er.java:84)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildMan
> ager.java:629)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(Bui
> ldManager.java:172)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(Bui
> ldManager.java:203)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildMan
> ager.java:255)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(Bui
> ldManager.java:258)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop
> (BuildManager.java:311)
> at org.eclipse.core.internal.events.BuildManager.build(BuildMan
> ager.java:343)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBu
> ildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJ
> ob.java:242)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
>

Re: NullPointerException in DefaultResourceDescriptionManager [message #662273 is a reply to message #637421]

Tue, 29 March 2011 22:30

Eclipse User

Sorry for dropping the ball on this... we just got hit by this problem again.
Other than sending all our source code and workbench contents (which I can't do), I don't really know how to extract a sample that would demonstrate the issue.

FWIW, after the exception, error markers no longer appear on the file icons (only in the editor), and we keep getting "empty" log entries in the log:

!ENTRY org.apache.log4j 4 0 2011-03-29 18:36:13.328
!MESSAGE org.eclipse.xtext.builder.impl.XtextBuilder -

Re: NullPointerException in DefaultResourceDescriptionManager [message #662482 is a reply to message #662273]

Wed, 30 March 2011 15:03

Eclipse User

We're also getting a similar stack trace when closing Xtext projects:

java.lang.NullPointerException
at org.eclipse.xtext.resource.impl.DefaultResourceDescriptionMa nager.isAffected(DefaultResourceDescriptionManager.java:112)
at org.eclipse.xtext.builder.builderState.ResourceDescriptionsU pdater.findAffectedResourceDescriptions(ResourceDescriptions Updater.java:189)
at org.eclipse.xtext.builder.builderState.ResourceDescriptionsU pdater.transitiveUpdate(ResourceDescriptionsUpdater.java:91)
at org.eclipse.xtext.builder.builderState.AbstractBuilderState. transitiveUpdate(AbstractBuilderState.java:163)
at org.eclipse.xtext.builder.builderState.PersistableResourceDe scriptionsImpl.doUpdate(PersistableResourceDescriptionsImpl. java:48)
at org.eclipse.xtext.builder.builderState.PersistableResourceDe scriptionsImpl.doUpdate(PersistableResourceDescriptionsImpl. java:1)
at org.eclipse.xtext.builder.builderState.AbstractBuilderState. update(AbstractBuilderState.java:111)
at org.eclipse.xtext.builder.impl.ProjectOpenedOrClosedListener $2$1.execute(ProjectOpenedOrClosedListener.java:134)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(Worksp aceModifyOperation.java:106)
at org.eclipse.core.internal.resources.Workspace.run(Workspace. java:1975)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(Workspac eModifyOperation.java:118)
at org.eclipse.xtext.builder.impl.ProjectOpenedOrClosedListener $2.run(ProjectOpenedOrClosedListener.java:146)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Could it be that the DefaultResourceDescriptionManager is instantiated directly (and not via Guice) under some circumstances?
Could one of our own components cause such a behavior?

Re: NullPointerException in DefaultResourceDescriptionManager [message #662488 is a reply to message #662482]

Wed, 30 March 2011 15:37

Eclipse User

Never mind, answered my own question here, it's one of our own components that is to blame...

Previous Topic:	sorting of grammar elements wrong after model modification
Next Topic:	Parsing comments

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 18 12:58:19 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter