Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » WindowBuilder » StackOverflowError in WindowBuilder
StackOverflowError in WindowBuilder [message #787498] Tue, 31 January 2012 11:47 Go to next message
Markus Schlegel is currently offline Markus Schlegel
Messages: 3
Registered: July 2009
Junior Member
Hi

I got a StackOverflowError while opening a UI in WindowBuilder Design Page:

!ENTRY org.eclipse.wb.core 4 4 2012-01-31 17:28:34.548
!MESSAGE Designer [1.2.0.r36x201109270310.201201311728]: java.lang.StackOverflowError
!STACK 0
java.lang.StackOverflowError
at java.lang.Exception.<init>(Exception.java:77)
at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:54)
at sun.reflect.GeneratedConstructorAccessor79.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at org.eclipse.wb.internal.core.utils.reflect.ReflectionUtils$ExceptionThrower.spit(ReflectionUtils.java:1284)
at org.eclipse.wb.internal.core.utils.reflect.ReflectionUtils.propagate(ReflectionUtils.java:1302)
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getJavaInfo(JavaInfoResolver.java:133)
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getExposedJavaInfo(JavaInfoResolver.java:306)
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getJavaInfo0(JavaInfoResolver.java:222)
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getJavaInfo(JavaInfoResolver.java:131)
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getExposedJavaInfo(JavaInfoResolver.java:306)
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getJavaInfo0(JavaInfoResolver.java:222)
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getJavaInfo(JavaInfoResolver.java:131)
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getExposedJavaInfo(JavaInfoResolver.java:306)
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getJavaInfo0(JavaInfoResolver.java:222)
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getJavaInfo(JavaInfoResolver.java:131)
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getExposedJavaInfo(JavaInfoResolver.java:306)
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getJavaInfo0(JavaInfoResolver.java:222)
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getJavaInfo(JavaInfoResolver.java:131)
at
...


The Problem is reproducable with that UI, but not with others (others just work fine).
I am using WindowBuilder in MyEclipse 10.

Markus
Re: StackOverflowError in WindowBuilder [message #787615 is a reply to message #787498] Tue, 31 January 2012 14:46 Go to previous messageGo to next message
Eric Clayberg is currently offline Eric Clayberg
Messages: 856
Registered: July 2009
Location: Boston, MA
Senior Member
Please provide a test case that will reproduce this exception.
Re: StackOverflowError in WindowBuilder [message #787618 is a reply to message #787615] Tue, 31 January 2012 14:49 Go to previous messageGo to next message
Markus Schlegel is currently offline Markus Schlegel
Messages: 3
Registered: July 2009
Junior Member
Can't provide one which compiles, since the code is not open source.
But from the Stacktrace, the problem seems to be obvious...
I mean
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getExposedJavaInfo(JavaInfoResolver.java:306)
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getJavaInfo0(JavaInfoResolver.java:222)
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getJavaInfo(JavaInfoResolver.java:131)
at org.eclipse.wb.internal.core.parser.JavaInfoResolver.getExposedJavaInfo(JavaInfoResolver.java:306)
...

Markus

[Updated on: Tue, 31 January 2012 14:49]

Report message to a moderator

Re: StackOverflowError in WindowBuilder [message #787653 is a reply to message #787618] Tue, 31 January 2012 15:58 Go to previous messageGo to next message
Eric Clayberg is currently offline Eric Clayberg
Messages: 856
Registered: July 2009
Location: Boston, MA
Senior Member
OK, if you think the problem is obvious, feel free to submit a patch. WB is open source after all. Wink

BTW, I would expect a patch to also include a test case that proves that the patch actually solves the problem.

It doesn't matter whether your specific code is open source or not. That is imaterial to providing a test case. If your current code triggers the problem, then it should be quite easy to construct a simple, standalone, dummy example that illustrates the exact same problem. Unless we have a way to actually reproduce the problem, there is really no point in spending time looking into it.

We are quite willing to look into this (and fix it), but only if we have the bare minimum of info needed to get started on it. That is what we need from you.

Re: StackOverflowError in WindowBuilder [message #787975 is a reply to message #787653] Wed, 01 February 2012 02:40 Go to previous messageGo to next message
Markus Schlegel is currently offline Markus Schlegel
Messages: 3
Registered: July 2009
Junior Member
Ok, then let it be like that and live with it. Eclipse was just asking me to send-in a Bugreport, what I did.
Can't do anything else.
BTW: WE did not buy Instantiations, and WE did not ask to make WB open source. But WE have been licensing WindowBuilder from Instantiations and we have already reported several Bugreports when it was an Instantiations Product.
We've been very disappointed as we heared that there won't be professional support anymore for WindowBuilder.
Re: StackOverflowError in WindowBuilder [message #788199 is a reply to message #787975] Wed, 01 February 2012 08:30 Go to previous message
Eric Clayberg is currently offline Eric Clayberg
Messages: 856
Registered: July 2009
Location: Boston, MA
Senior Member
In that case, why send in a partial bug report and exclude the test case?

If you have a class that exhibits this problem, creating a test case that will reproduce that same problem should not take more than a few minutes.

I'm not sure why you would be disappointed with the level of support, since we are offerring to do just that. In fact, the very same team that worked on and supported WB before it was open sourced still works on and supports it now. I believe that our track record for responding to user questions and fixing bugs has been exceptional. We respond to almost every forum message, and we have closed 94% of bug reports in Bugzilla.

As I said earlier, we are more than willing to look into this, but you have to give us something to work with. Please read Reproducible Test Cases in the WB docs, if you need a further explanation of why this is important.
Previous Topic:WindowBuider gives java.lang.NoClassDefFoundError: org/eclipse/jdt/core/dom/AnonymousTypeDeclaration
Next Topic:Resize Tool not Working
Goto Forum:
  


Current Time: Thu Aug 21 22:11:35 EDT 2014

Powered by FUDForum. Page generated in 0.01695 seconds