Stack overflow at line 0

[Alex]

A browser native popup dialog shows "Stack overflow at line 0".

This has started happening for no apparent reason in GWT hosted mode
(using IE6) right after my application loads.

This doesn't hapen in compiled mode neither on Firefox nor IE6.

Apparently nondeterministic behavior occurs after this error - most of
the time my application works fine, but sometimes there are layout
problems and once I got a NullPointerException.

There have been a few threads on this already, but no substantial
response from the GWT team. Are you guys still baffled by this issue?

[Alex]

P.S. I have reason to believe that this error occurs during RPC,
*both* during serialization and deserialization on the client side.

Another clue - I have recently added java.io.Serializable (via the
GWTx addon lib) to my DTOs implements list (so I could write them to
disk), in addition to IsSerializable. I wonder if that may have
something to do with it.

- Alex

[Miguel Méndez]

Hello Alex,

I do recall that we had some problems with cyclic object graphs is earlier versions of GWT; pre 1.2 I believe.  Version 1.3.3 does not have these problems.  There was also a thread which reported this error for GWT version 1.2.11.  Here is a link to the thread: http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/9d130ee8656073f3 . 

What version of GWT are you using?  Do the objects that you are sending over RPC have cyclic references?  If you have code that can reproduce this please let me know, and I can look into it. 

--
Miguel

[Alex]

Hi Miguel,

I am using 1.3.3, and indeed, the error started occurring after I
added cycles to my DTOs (objects sent over RPC).

It's an e-commerce app, with a Category class which contains a
collection of Item instances. Each Item instance, in turn, contains a
collection of references to the Category instances to which it
belongs.

So it's a many-to-many relationship between Categories and Items.

Could it be a case of that same problem you thought was fixed?

Thanks for your response,
Alex

On Apr 9, 9:11 am, "Miguel Méndez" <mmen...@google.com> wrote:
> Hello Alex,
>
> I do recall that we had some problems with cyclic object graphs is earlier
> versions of GWT; pre 1.2 I believe. Version 1.3.3 does not have these
> problems. There was also a thread which reported this error for GWT version

> 1.2.11. Here is a link to the thread:http://groups.google.com/group/Google-Web-Toolkit/browse_thread/threa....

>
> What version of GWT are you using? Do the objects that you are sending over
> RPC have cyclic references? If you have code that can reproduce this please
> let me know, and I can look into it.
>

[Miguel Méndez]

Hi Alex,

I created a simple test case based on your explanation to see if I could reproduce this problem on 1.3.3.  I was unable to do so on XP or Linux.  Modifying the example to call the service directly from the onModuleLoad instead of an onClick handler had no impact.

I have attached the project; please advise if it reproduces the problem for you.  It may ultimately be better to provide me with some example code that demonstrates the problem.  We do not need the whole app just the service interfaces, the classes that you exchange with the service and some code to setup the test.  Ideally, this could take the form of a JUnit test case which we can run.

Cheers,

--
Miguel

[Alex]

Okay, I will try to isolate the issue. In the meantime, is there a
way I could help by debugging? Perhaps you could tell me where I
could set some breakpoints and what to watch for?

Thanks,
Alex

On Apr 10, 11:37 am, "Miguel Méndez" <mmen...@google.com> wrote:
> Hi Alex,
>
> I created a simple test case based on your explanation to see if I could
> reproduce this problem on 1.3.3. I was unable to do so on XP or Linux.
> Modifying the example to call the service directly from the onModuleLoad
> instead of an onClick handler had no impact.
>
> I have attached the project; please advise if it reproduces the problem for
> you. It may ultimately be better to provide me with some example code that
> demonstrates the problem. We do not need the whole app just the service
> interfaces, the classes that you exchange with the service and some code to
> setup the test. Ideally, this could take the form of a JUnit test case
> which we can run.
>
> Cheers,
>

> CyclicReferences.tar.gz
> 5KDownload