If you do some searching on this I think you will find that it is related to javascript code that is making recursive or repeated calls to the same javascript method. I think IE is treating this as some sort of warning/error to guard itself against potential stack overflow problems. I have chased this problem for many hours. Happens frequently in IE 6 but less of an issue in IE7 and probably related to javascript performance. I think I remember this was an issue in google generated RPC code that may have been fixed in GWT 1.5.x. Search on stack overflow in the message group and you should be able to find it.
Thanks Scooter Willis On Feb 5, 1:50 pm, Barry <[email protected]> wrote: > Thanks, Paul ... > > ... some perspective is a help. > > Yes, I realize that OOPHM will at least allow me to switch to FireFox > for hosted mode, and that's a good thing. But GWT2.0 isn't here yet, > so for now, I think I'll have to flatten the tree for marshalling and > then reinflate it in the browser ... not a very welcome diversion, > especially for short term code. > > Thanks for the corroboration ... and if anyone else can add in, please > do! > > On Feb 5, 1:00 am, Paul Robinson <[email protected]> wrote: > > > Barry wrote: > > > Hi ... > > > > I'm getting a message box from Internet Explorer after executing the > > > handler for an RPC call. The message box says "Stack overflow at line: > > > 0". The data being returned is a tree. If the tree isn't returned, I > > > don't get the message box. > > > > There are several threads on this issue going back to 2006 and as late > > > as December 2008. > > > > Apparently, this is a bug in the IE stack overflow detection. I'm > > > running IE 7, and the problem occurs in hosted mode. > > > > Is there any resolution to this problem?? It's pretty serious ... I > > > mean to send a lot of these trees around. > > > > Is there any workaround?? > > > Until I recently switched to linux, I got this all the time once my > > project got to a certain size....but only in hosted mode and it never > > appeared to have any side-effects anything apart from producing the > > pop-up. I've seen no workaround. Previous searches through the threads > > left me wondering whether this affects everyone on windows with large > > projects or whether there's some other environmental trigger. > > > Roll on GWT2.0 and OOPHM. > > > Paul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
