Bugzilla – Full Text Bug Listing
| Summary: | Xtend is incredibly slow if Papyrus is installed | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Ed Willink <ed> |
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | cletavernier, vlad.gheorghe |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| See Also: |
https://bugs.eclipse.org/bugs/show_bug.cgi?id=486083 https://bugs.eclipse.org/bugs/show_bug.cgi?id=352688 |
||
| Whiteboard: | |||
Restarting Eclipse, opening and closing a Papyrus editor and all is ok again, so no easy repro; just the stack trace. Similar bug: #352688 See Bug 420384 for an explanation of how every possible Xtext editor may be activated every time JDT can be 'helped'. Xtend of course makes extensive use of JDT 'help'. Perhaps aggravated by Bug 486083 |
Kepler. In order to diagnose bad build issues I am running with a console showing org.eclipse.core.resources/debug=true org.eclipse.core.resources/build/stacktrace=true org.eclipse.core.resources/build/invoking=true org.eclipse.core.resources/build/delta=true org.eclipse.core.resources/build/needbuild=true org.eclipse.core.resources/build/needbuildstack=true org.eclipse.jdt.core/debug=true org.eclipse.jdt.core/debug=true org.eclipse.jdt.core/debug/builder=true org.eclipse.jdt.core/debug/builder/stats= true which enables me to get some clues as to why Xtend is brick-like. With no Papyrus editors active, the following keeps appearing amongst many build activities! 1 error 4727549 [main] ERROR org.eclipse.papyrus.uml.textedit.parameter.xtext.ui.UmlParameterExecutableExtensionFactory - com.google.inject.ProvisionException: Guice p 1) Error injecting constructor, org.eclipse.core.runtime.AssertionFailedException: null argument:I can't find the edited element at org.eclipse.papyrus.uml.textedit.parameter.xtext.scoping.UmlParameterScopeProvider.<init>(Unknown Source) while locating org.eclipse.papyrus.uml.textedit.parameter.xtext.scoping.UmlParameterScopeProvider while locating org.eclipse.xtext.scoping.IScopeProvider for field at org.eclipse.xtext.ui.editor.quickfix.DefaultQuickfixProvider.scopeProvider(Unknown Source) while locating org.eclipse.papyrus.uml.textedit.parameter.xtext.ui.quickfix.UmlParameterQuickfixProvider while locating org.eclipse.xtext.ui.editor.quickfix.IssueResolutionProvider for field at org.eclipse.xtext.ui.editor.quickfix.AbstractIssueResolutionProviderAdapter.resolutionProvider(Unknown Source) while locating org.eclipse.xtext.ui.editor.quickfix.MarkerResolutionGenerator 1 error Why is Xtext waking Papyrus up to burn cycles?