Community
Participate
Working Groups
Hello committers, we received a new error report for Eclipse 4.4.0.I20140606-1215. General Information: anonymous-id: e01d726b-3343-432c-ba0c-54555eed76a0 eclipse-build-id: 4.4.0.I20140606-1215 eclipse-product: org.eclipse.epp.package.jee.product operating system: Linux 3.13.0 (x86_64) - gtk java-runtime-version: 1.7.0_65-b32 The following plug-ins were present on the execution stack (*): 1. org.eclipse.core.runtime_3.10.0.v20140318-2214 2. org.eclipse.jdt.core_3.10.0.v20140902-0626 3. org.eclipse.jdt_3.10.0.v20140925-0400 4. org.eclipse.jdt.ui_3.10.1.v20140817-1500 5. org.eclipse.jface.text_3.9.0.v20140521-1657 6. org.eclipse.jface_3.10.0.v20140604-0740 Error Status: code: 2 plugin: org.eclipse.jdt.core_3.10.0.v20140902-0626 message: Problems occurred when invoking code from plug-in: "org.eclipse.jdt.core". fingerprint: 85fbd39d exception class: org.eclipse.core.runtime.AssertionFailedException exception message: null argument: number of children: 0 org.eclipse.core.runtime.AssertionFailedException: null argument: at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85) at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73) at org.eclipse.jdt.ui.text.folding.DefaultJavaFoldingStructureProvider.computeCurrentStructure(DefaultJavaFoldingStructureProvider.java:1388) at org.eclipse.jdt.ui.text.folding.DefaultJavaFoldingStructureProvider.update(DefaultJavaFoldingStructureProvider.java:886) at org.eclipse.jdt.ui.text.folding.DefaultJavaFoldingStructureProvider.access$9(DefaultJavaFoldingStructureProvider.java:876) at org.eclipse.jdt.ui.text.folding.DefaultJavaFoldingStructureProvider$ElementChangedListener.elementChanged(DefaultJavaFoldingStructureProvider.java:361) at org.eclipse.jdt.internal.core.DeltaProcessor$4.run(DeltaProcessor.java:1695) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1685) at org.eclipse.jdt.internal.core.DeltaProcessor.fireReconcileDelta(DeltaProcessor.java:1537) at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1496) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:770) at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:789) at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1247) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:126) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.access$0(JavaReconcilingStrategy.java:108) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy$1.run(JavaReconcilingStrategy.java:89) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:87) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:151) at org.eclipse.jdt.internal.ui.text.CompositeReconcilingStrategy.reconcile(CompositeReconcilingStrategy.java:86) at org.eclipse.jdt.internal.ui.text.JavaCompositeReconcilingStrategy.reconcile(JavaCompositeReconcilingStrategy.java:104) at org.eclipse.jface.text.reconciler.MonoReconciler.process(MonoReconciler.java:77) at org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:206) Messages, stacktraces, and nested status objects may be shortened. Please visit http://dev.eclipse.org/recommenders/committers/confess/0.5/reports/- for the complete error log. Some general information and guidelines about how to use this bug report: 1. Feel free to move this bug to your own product and components. Please note that this bug is only accessible to Eclipse committers. If you move this bug please make sure that it's still in the "Security Advisor" group. 2. The bug contents of the fields status, resolution, keywords, and whitelist are presented to reporters. If you needs more information, please set the keyword "needinfo". This will trigger a specialized dialog asking the user to provide further details. 3. Use the following resolutions for the following situations: * CLOSED / FIXED: This bug has been fixed. Please provide additional information in the whiteboard field. * CLOSED / WORKSFORME: Use this resolution if you can't reproduce this issue and request further information. Please use the whiteboard text to specify more details what a user should provide and how. * CLOSED / INVALID: Use this resolution if the reported problem is a 'user-configuration' problem. Please consider giving hints how to fix these issues in the whiteboard field. * CLOSED / NOT ECLIPSE: Use this if the problem is caused by another plugin not developed at Eclipse.org * CLOSED / MOVED: If this bug has been moved else where. Please provide more information (e.g. a link) in the whiteboard field. 4. Please remember that only committers can view and comment on this bug. You may, however, manually add the reporting user to the bug's cc list. But keep in mind that the report may contains sensitive information. 5. If you are missing a feature, please file a enhancement request here: https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Recommenders.Incubator&component=Stacktraces Thank you for your assistance. Your friendly error-reports-inbox. -- * Note: The list of present bundles and their respective versions was calculated by package naming heuristics. This may or may not reflect reality.
I've looked up the (to date) top-3 most similar bug groups and listed the closest bug of each group below. This report may or may not be duplicate of those (low or similar scores for all entries may indicate that this hasn't been reported yet): > 1. Bug 448402: [jpt] NPE in AbstractJpaProject.compilationUnitResourceExists – 0,8 > 2. Bug 449729: [platform] Error in JDT Core during reconcile – 0,6 > 3. Bug 448381: [platform] Exception occurred during problem detection: --------------------------------... – 0,6 If this report actually is a duplicate of those, please mark it as such. This information helps me to improve the recommendations further for the next issue. Thank you for your assistance. Your friendly error-reports-inbox.
Moving to JDT for review.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
