Re: How to diagnose IE8 javascript error stack overflow at line: 0? ends up in Impl.entry0
Thanks for your reply. That is interesting. For a long time, I thought it was due to my use of the Raphael-gwt library. But now I've removed that, and still get the error. And I _am_ bringing back some large and complex objects via RPC, so I'll look into that. On Nov 6, 3:50 am, Didier DURAND durand.did...@gmail.com wrote: Hi, I don't know enough about your appl but we had similar issues: that was due to complex data structures that we were bringing back to the client from the server over the GWT RPC - we had to simplify the structures (carrying simple arrays of objects rather than complex graphs over RPC) in order to avoid the stack overflow caused by GWT- RPC serialization/deserialization. You may have a look in that direction too. Hope it helps. didier On Nov 5, 8:22 pm, BrianP brifo...@gmail.com wrote: I have a GWT 2.0.3 app that runs fine in Firefox and Chrome. But when run in IE8 I get a javascript error that pops up with 'Stack over flow at line: 0'. When stepping through it in debug mode, I end up in GWT class Impl in the method entry0(Object jsFunction, Object thisObj, Object arguments). I was hoping to find more information by looking at those variables in debug mode, but they didn't really tell me anything other than its a JavaScriptException, which I already knew. Any recommendation on how I might get more information on this error? It seems similar to the error in this thread: http://groups.google.com/group/google-web-toolkit/browse_thread/threa... One response there mentions adding an UncaughtExceptionHandler there to the main EntryPoint class. Would that help? Thanks -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: How to diagnose IE8 javascript error stack overflow at line: 0? ends up in Impl.entry0
It looks like this is the case - a large/complex object over RPC causing the problem. I commented out that call to the server, and the component loaded fine. So the next question is: how do you know your objects are too large for RPC? Where is the threshhold? On Nov 8, 10:40 am, BrianP brifo...@gmail.com wrote: Thanks for your reply. That is interesting. For a long time, I thought it was due to my use of the Raphael-gwt library. But now I've removed that, and still get the error. And I _am_ bringing back some large and complex objects via RPC, so I'll look into that. On Nov 6, 3:50 am, Didier DURAND durand.did...@gmail.com wrote: Hi, I don't know enough about your appl but we had similar issues: that was due to complex data structures that we were bringing back to the client from the server over the GWT RPC - we had to simplify the structures (carrying simple arrays of objects rather than complex graphs over RPC) in order to avoid the stack overflow caused by GWT- RPC serialization/deserialization. You may have a look in that direction too. Hope it helps. didier On Nov 5, 8:22 pm, BrianP brifo...@gmail.com wrote: I have a GWT 2.0.3 app that runs fine in Firefox and Chrome. But when run in IE8 I get a javascript error that pops up with 'Stack over flow at line: 0'. When stepping through it in debug mode, I end up in GWT class Impl in the method entry0(Object jsFunction, Object thisObj, Object arguments). I was hoping to find more information by looking at those variables in debug mode, but they didn't really tell me anything other than its a JavaScriptException, which I already knew. Any recommendation on how I might get more information on this error? It seems similar to the error in this thread: http://groups.google.com/group/google-web-toolkit/browse_thread/threa... One response there mentions adding an UncaughtExceptionHandler there to the main EntryPoint class. Would that help? Thanks -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: How to diagnose IE8 javascript error stack overflow at line: 0? ends up in Impl.entry0
Hi Brian, I don't have exact figures but what I know is that some structures (Java collections) needs tons of Javascript stack entries to get serialized / deserialized: knowing that , our strategy is to carry single objects or arrays (even of hetegeneous objects) on the wire and reconstruct the more complex structures either on client or server side. regards didier On Nov 8, 8:14 pm, BrianP brifo...@gmail.com wrote: It looks like this is the case - a large/complex object over RPC causing the problem. I commented out that call to the server, and the component loaded fine. So the next question is: how do you know your objects are too large for RPC? Where is the threshhold? On Nov 8, 10:40 am, BrianP brifo...@gmail.com wrote: Thanks for your reply. That is interesting. For a long time, I thought it was due to my use of the Raphael-gwt library. But now I've removed that, and still get the error. And I _am_ bringing back some large and complex objects via RPC, so I'll look into that. On Nov 6, 3:50 am, Didier DURAND durand.did...@gmail.com wrote: Hi, I don't know enough about your appl but we had similar issues: that was due to complex data structures that we were bringing back to the client from the server over the GWT RPC - we had to simplify the structures (carrying simple arrays of objects rather than complex graphs over RPC) in order to avoid the stack overflow caused by GWT- RPC serialization/deserialization. You may have a look in that direction too. Hope it helps. didier On Nov 5, 8:22 pm, BrianP brifo...@gmail.com wrote: I have a GWT 2.0.3 app that runs fine in Firefox and Chrome. But when run in IE8 I get a javascript error that pops up with 'Stack over flow at line: 0'. When stepping through it in debug mode, I end up in GWT class Impl in the method entry0(Object jsFunction, Object thisObj, Object arguments). I was hoping to find more information by looking at those variables in debug mode, but they didn't really tell me anything other than its a JavaScriptException, which I already knew. Any recommendation on how I might get more information on this error? It seems similar to the error in this thread: http://groups.google.com/group/google-web-toolkit/browse_thread/threa... One response there mentions adding an UncaughtExceptionHandler there to the main EntryPoint class. Would that help? Thanks -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: How to diagnose IE8 javascript error stack overflow at line: 0? ends up in Impl.entry0
Hi, I don't know enough about your appl but we had similar issues: that was due to complex data structures that we were bringing back to the client from the server over the GWT RPC - we had to simplify the structures (carrying simple arrays of objects rather than complex graphs over RPC) in order to avoid the stack overflow caused by GWT- RPC serialization/deserialization. You may have a look in that direction too. Hope it helps. didier On Nov 5, 8:22 pm, BrianP brifo...@gmail.com wrote: I have a GWT 2.0.3 app that runs fine in Firefox and Chrome. But when run in IE8 I get a javascript error that pops up with 'Stack over flow at line: 0'. When stepping through it in debug mode, I end up in GWT class Impl in the method entry0(Object jsFunction, Object thisObj, Object arguments). I was hoping to find more information by looking at those variables in debug mode, but they didn't really tell me anything other than its a JavaScriptException, which I already knew. Any recommendation on how I might get more information on this error? It seems similar to the error in this thread: http://groups.google.com/group/google-web-toolkit/browse_thread/threa... One response there mentions adding an UncaughtExceptionHandler there to the main EntryPoint class. Would that help? Thanks -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
