Community
Participate
Working Groups
2018-12 M1: After closing some Plugin (Java) Projects the Error Log is cluttered with top level "Advanced source lookup task failed" entries with sub-errors identifying each closed project. This is normal. No need for error logging. No Stack trace available.
Can you please provide error log?
Created attachment 276578 [details] .log file (Breakpoint does not have an associated marker is also a problem but probably due to removal of the target file from the classpath. Perhaps even deletion of the target file which was auto-generated.) (org.eclipse.xtext.resource.impl.DefaultResourceDescriptionStrategy - Reference from platform:/resource/org.eclipse.qvtd.compiler/org/eclipse/qvtd/compiler/internal/qvtr2qvtc/RelToCoreRevised.qvtr#//@ownedTransformations.0/@ownedQueries.2/@ownedExpression/@ownedInExpression/@ownedElseExpression/@ownedThenExpression/@ownedInExpression/@ownedRight/@ownedRight/@ownedRoundBracketedClause/@ownedArguments.0/@ownedNameExpression/@ownedRight/@ownedRight/@ownedRoundBracketedClause/@ownedArguments.1/@ownedNameExpression/@ownedPathName/@ownedPathElements.0 to avs cannot be exported as the target is not contained in a resource. is something different perhaps Xtext, perhaps QVTd but what is "avs".)
From !ENTRY org.eclipse.jdt.launching 4 4 2018-11-14 20:59:48.705 !MESSAGE Advanced source lookup task failed !SUBENTRY 1 org.eclipse.jdt.core 4 969 2018-11-14 20:59:48.705 !MESSAGE org.eclipse.qvtd.umlx.design does not exist ... I'd hazard a guess that advance source lookup asks jdt.core s.t. about project org.eclipse.qvtd.umlx.design, which is nowhere to be found for jdt.core. After seeing loads of messages about missing .project I wonder in what state that workspace is? Do the projects reported as "does not exist" exist in the workspace? If not, who/what might be referencing them? Some stale launch configuration?
I couldn't provide the original log since it was so cluttered that I deleted it. I reproduced the problem just by opening many projects and then closing them again, so the problem projects are in the workspace, but have been closed. (If nothing else there is a bug in regard to the missing stack trace.)
Created attachment 279042 [details] Another .log file Still happens on 2019-06 Happens when I do a multi-project (perhaps 40 projects in 6 working sets) close. Looks as if some idiot tooling is trying to refresh while major existence changes are in progress. Might explain why Close Project is really really slow.
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.
