We do both: release compiles have a permutation with native stack traces for normal use, plus a "debug" version which includes emulated stack traces. We deploy both of them, but don't tell real users about the debug version unless there's a good reason to do so.
Sometimes it's useful for us to be able to switch to the debug compile when you have a repeatable error to get a higher quality stack trace. It means our internal releases for testing are identical to what gets released externally. On Thu, Nov 30, 2017 at 8:49 AM, Jens <[email protected]> wrote: > > OMG 50%, hehe maybe I did something wrong last time I was checking the >> difference. I need to try it again. Thanks! >> > > Yes it is always twice the size because GWT compiler will insert an > additional line of code to capture stack frames for each line of your code. > For small apps it is not that dramatic but for example our app would grow > multiple mega bytes and execution will noticeably slow down. Thus we don't > use emulated stack traces. But event without it we can still find the > reason for an exception relatively quickly. > > -- J. > > -- > 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. > -- 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.
