Hello,
This is really just a heads up...
We are currently developing a large/complex GWT app and are making use
of ClientBundle, CssResource and ImageResource. We've run into an
issue where by GWT is generating massive sprite images (for instance
one is 163,000 x 300 pixels) - which obviously
Did you check your Compile reports ?
http://code.google.com/webtoolkit/release-notes.html#Release_Notes_2_0_0_rc2
On Jul 9, 1:55 pm, DaveC david.andrew.chap...@googlemail.com wrote:
Hello,
This is really just a heads up...
We are currently developing a large/complex GWT app and are making
No, forgot about those (I check them)... but I have some more info
now... I can trigger the big sprites by changing the size of the image
(thats repeated) e.g.
image 62 x 60 px triggers big sprite
image 500 x 60 px no big sprite...
On Jul 9, 1:02 pm, Frederic Conrotte
Checked the compile report, but I can't seem to find where it
references (if it even does) the generated ImageResourceBundles...
On Jul 9, 1:58 pm, DaveC david.andrew.chap...@googlemail.com wrote:
No, forgot about those (I check them)... but I have some more info
now... I can trigger the big
Hi Dave,
163000x300 pixel is extreme.
I see two causes
a) you have such a lot images. Than I would try for splitting up the
ClientBundle
b) GWT has a bug which causes huge images as a result. Maybe a) puts
the compiler in a more stable state
Stefan Bachert
http://gwtworld.de
On 9 Jul.,
Yeh, we were seeing browser memory usage jump from about 40Mb to over
300Mb.
We already split images/resources up (into modules/plugins with
specific functionality e.g. Search, RSSFeed, AppFramework etc, etc) -
for example in one bundle there are 17 images (9 of those are for a
DecoratorPanel, 5
