Well, all I can say for sure is that it also happens on 2.6.0, and that it seems somehow tied to the particular configuration of our large slaves.
So, given I don't have reproduction instructions beyond "run a gwt compile on our code on a particular configuration of our infrastructure", I'd have to say you can safely ignore this. Still, it beats me how simply changing the instance size (amd from 32 to 64 bits) can affect a stack overflow like this... -- This message and any attachments are solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use, or distribution of the information included in this message is prohibited -- please immediately and permanently delete this message. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/824b9af9-86fd-4403-bc1a-91e63eaca347%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
