Bug 415284 - Xtend is incredibly slow if Papyrus is installed
Summary: Xtend is incredibly slow if Papyrus is installed
Status: NEW
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-17 14:36 EDT by Ed Willink CLA
Modified: 2017-06-26 10:19 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2013-08-17 14:36:37 EDT 
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?
Comment 1 Ed Willink CLA 2013-08-17 16:57:46 EDT 
Restarting Eclipse, opening and closing a Papyrus editor and all is ok again, so no easy repro; just the stack trace.
Comment 2 Vlad Gheorghe CLA 2013-09-26 08:08:50 EDT 
Similar bug: #352688
Comment 3 Ed Willink CLA 2013-10-26 06:38:20 EDT 
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'.
Comment 4 Ed Willink CLA 2017-06-26 10:19:07 EDT 
Perhaps aggravated by Bug 486083