Re: GWT application runtime memory size is too large (client side)

[Andrei]

Do you use code-splitting? Do you use Activities and Places design pattern? Do you use i18n, and if you do, dynamic or static? Is there a lot of text in some views? Do you use CellTable or DataGrid widgets, and if you do, how much data is displayed in each of them? Do you have complex views with multiple nested panels (i.e. VerticalPanel inside HorizontalPanel, etc.)?

 

You gave us very little information about your app. There are many ways to optimize memory use.

[Frank Hossfeld]

Did you check the execution time of your app? iOS 6 limits the JavaScript execution time to 10 seconds  for each top-level entry point.

Am Freitag, 28. Dezember 2012 13:28:21 UTC+1 schrieb mkn:

I have written quite a sophisticated gwt application (many different views, combined with highcharts). Since ios6 I have observed that sometimes the application crashes in safari. After debugging for quite a while I read somewhere that safari limits the memory size to 10MB. Therefore I used the profile function of chrome to take a heap snapshot. The result is that my application has a size of 9.55MB (!!). Sometimes it seems to exceed the 10MB and then the safari browser crashes.

Therefore I obviously need somehow to shrink the size (it is about runtime memory size). Any suggestions :)? Or is the conclusion somehow, that GWT is not suitable for "very large" applications? 

P.S.

I have not discovered any memory leeks in the application.

[Benjamin Possolo]

+1 to this

code splitting will be the biggest improvement you can make. if you are using activities/places then it is easy to introduce split points around every activity (using AsyncProxy).

If your UiBinder templates are innefficiently written then it will impact memory a lot. prefer using HTMLPanel at the top of most uibinder views and then use raw html as often as possible instead of gwt widgets.

also when gwt compiling, make sure you are producing obfuscated javascript rather than pretty or detailed