Eclipse Community Forums: Eclipse 4 » E4 is constantly destroying workspaces

Help

Home

Home » Eclipse Projects » Eclipse 4 » E4 is constantly destroying workspaces

Show: Today's Messages :: Show Polls :: Message Navigator

E4 is constantly destroying workspaces [message #1776763]

Tue, 21 November 2017 11:22

philipp huebner

Messages: 65
Registered: July 2009

Member

Hi together,

we have some serious problems with e4, 4.6.3. ...
After starting our RCP multiple times, something destroys the workspaceand we getting weird exeptions, with these total reasonable dependency injection stacktraces which are so helpful...

!ENTRY org.eclipse.e4.ui.workbench.swt 4 2 2017-11-21 12:18:17.248
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.e4.ui.workbench.swt".
!STACK 0
org.eclipse.e4.core.di.InjectionException: java.lang.IllegalArgumentException: 
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:65)
	at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:966)
	at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151)
	at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:118)

I don't know a solution for it, nothing works. It costs us a lot of time and we cannot deliver a e4 bases product to our customers because of that behavoiour. Is there any patch for that or something we could do?

Report message to a moderator

Re: E4 is constantly destroying workspaces [message #1776770 is a reply to message #1776763]

Tue, 21 November 2017 12:40

philipp huebner

Messages: 65
Registered: July 2009

Member

This is the causing problem. It appears in different projects and happens per developer at least one time a week. Sometimes new workspace helps, sometimes take a new eclipse verison, sometimes deleting some plugins from workspace.

!ENTRY org.eclipse.e4.ui.workbench 4 0 2017-11-21 13:37:41.456
!MESSAGE Exception occurred while rendering: org.eclipse.e4.ui.model.application.ui.basic.impl.TrimmedWindowImpl@582a764a (elementId: IDEWindow, tags: [topLevel], contributorURI: platform:/plugin/org.eclipse.ui.workbench) (widget: Shell {Veo}, renderer: org.eclipse.e4.ui.workbench.renderers.swt.WBWRenderer@7dd91ffc, toBeRendered: true, onTop: false, visible: true, containerData: null, accessibilityPhrase: null) (label: null, iconURI: null, tooltip: null, context: TrimmedWindowImpl (IDEWindow) Context, variables: [], x: 50, y: 50, width: 800, height: 600)
!STACK 0
org.eclipse.e4.core.di.InjectionException: java.lang.IllegalArgumentException: 
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:65)
	at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:966)

Report message to a moderator

Re: E4 is constantly destroying workspaces [message #1776776 is a reply to message #1776770]

Tue, 21 November 2017 14:25

Eclipse User

The injector wraps an exception in an InjectionException, so the original exception's stack trace should appear below. If all else fails, put an exception breakpoint on IllegalArgumentException and/or InjectionException.

Report message to a moderator

Re: E4 is constantly destroying workspaces [message #1776786 is a reply to message #1776776]

Tue, 21 November 2017 15:53

Eclipse User

Another possibility: Sun JVMs may optimize away stack traces, but this only happens when a method is optimized because it's called several times already. So the error stack trace may have occurred previously.

http://jawspeak.com/2010/05/26/hotspot-caused-exceptions-to-lose-their-stack-traces-in-production-and-the-fix/

Otherwise you could also try running with `-XX:-OmitStackTraceInFastThrow`.

Brian.

Report message to a moderator

Previous Topic:	E4Application ActiveChild RAT
Next Topic:	Parts background color with gradient

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed Apr 24 17:20:58 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter