Thursday, May 31, 2012

Resolving client issues when emulated stack trace is not available

I'm looking for practical advice here; we have a GWT application in pre-production pilot.
It is working rather well, but occasionally transient client errors occur.
We are using an uncaught exception handler, but the information that it reports is 
very sparse (For example in IE6, "Object doesn't support this property or method")

I've tried turning on emulated stack traces in development, but due to performance
I haven't been able to leave it turned on, and therefore it is not active in the pilot environment.

What else I can do to track down these issues?  In one case the problem consistently happens 
on 2 or 3 client machines, but not on any of the others.

Regarding the practical usability of emulated stack traces, I'm surprised that no one else seems
to have reported this problem.  Only yesterday I had a similar experience in development where
I thought using emulated stack traces would save the day, only to be disappointed again that
turning them on made the application unusable.  (I believe this is a client memory issue)
Should I open a GWT issue?  A possible enhancement that comes to mind is to create emulated
stack traces only for certain packages, to conserve memory.


You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

No comments:

Post a Comment