You might want to generate a compile report and check memory size for the compiled code: http://code.google.com/webtoolkit/doc/latest/DevGuideCompileReport.html.
As for the actual data, any javascript profiler will work, you will want to compile with the -pretty option to get legible function names. On May 28, 11:12 am, Twentyseven <[email protected]> wrote: > Hello, > > We're developing a very big application using GWT and we're facing big > memory usage by the browser (sometime 2 Gb on Chrome). > How could I profile/monitor the use of monitor and determine what are > the composite who take the memory ? > > thank's -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
