About production issue: Are you sure about this? It's less likely to happen in production since many clinit calls will have been stripped by the compiler, but its probably still going to happen.
About development: Is there actually a global try catch in your code or is this even something else? I am not really familiar with the old GWT linkers anymore and how they outputted code. On Wednesday, April 6, 2016 at 4:47:45 PM UTC+2, TazmanianD wrote: > > Thanks so much for the response! You say "all modern versions of GWT". I > don't suppose you can be more specific? The 2.8 version hasn't been > released yet and we can't upgrade to pre-release versions. We can probably > give the beta version a try just to see if it does fix our problem. Is this > problem fixed in 2.7? We've been waiting for 2.8 before undertaking the > upgrade but it sounds like we need to jump to 2.7 now. > > Fortunately for us, this isn't (apparently) a production issue for us yet > so we're not in an emergency mode but I gather others may not be so lucky. > I posted a reply to a question in the Chrome forum where someone was using > GWT 1.6 and upgrading may be even harder for this. I don't suppose you have > any other advice for anyone else who may stumble across this and not have > an immediate path to upgrade? > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
