It should sound weird, but... have you tried to compile with less memory at -Xmx parameter?
Try the default -Xmx128m, and others like -Xmx512m, -Xmx1024m or -Xmx8192m This came from here "It's more that the JVM allocates multiple regions of memory. When you increase -Xmx, this can cause some of the other ones to shrink." I'll keep researching for an answer for this issue. -- Francisco Bischoff http://www.cirurgiaplastica.pro.br "O mate está para o gaúcho como o chá para os ingleses, a coca para os bolivianos, o uísque para os escoceses e o café... para os brasileiros" -- Eduardo Bueno On Tue, Jan 26, 2010 at 2:08 PM, Pieter Breed <[email protected]>wrote: > Sorry, I just read what I worte and realised I made a mistake. We > don't have that many .properties files, but we do have a large (> > 1000) files that describe each field in the DTO with a constant string > value. Ex: > > public class AdminUserListDefProperties implements Serializable, > BeanModelTag { > public final static String Name = "Name"; > } > > describes a class AdminUserListDef, which has one property, ie, getName > () and setName(). > > We have about a thousand of these (our data model is pretty huge) but > they are only used on the server, not on the client > > Pieter > > On Jan 26, 3:43 pm, Pieter Breed <[email protected]> wrote: > > This is the original v1.7 code with only the GWT 2 change applied, ie > > no other code changes have been applied yet. > > > > We are able to run the app in dev mode without any issues. > > > > We use a few 3rd party modules, yes. The primary client-side > > dependency is the GXT module. On the server we have a few other > > dependencies: > > - ehcache > > - derby > > - jna > > > > We do have a large number of codegen files. We have a 3rd party middle- > > ware component that we use for comms, which allows us to have clients > > for the server in many languages. We use this technology to codegen > > XML serializers and DTOs. This pipeline is on the server, from where > > normal GWT rpc is used to communicate with the client via the API > > service calls. For most of these DTO's we create .properties files > > that help us to create beans to which we can bind the UIs. > > > > Does this information help? > > > > Pieter > > > > On Jan 26, 2:35 pm, Francisco Bischoff <[email protected]> > > wrote: > > > > > > > > > The code you are trying to compile is the original from GWT 1.7 project > or > > > have you made some changes? What about the 3rd party modules, do you > use > > > some of that? Maybe there is some code messing up with the compiler... > > > > > And the Development Mode, can you try the application using it? > > > > > Try to compile your code as original as you had successfully compiled > in GWT > > > 1.7 and try to make experiments cutting some 3rd party modules off. > > > > > -- > > > Francisco Bischoffhttp://www.cirurgiaplastica.pro.br > > > > > "O mate está para o gaúcho como o chá para os ingleses, a coca para os > > > bolivianos, o uísque para os escoceses e o café... para os brasileiros" > > > -- Eduardo Bueno > > > > > On Mon, Jan 25, 2010 at 10:45 AM, Pieter Breed <[email protected] > >wrote: > > > > > > Hi Frincisca, > > > > > > Yes, actually... My machine is currently trying to build the app with > > > > an allocated 15Gigabytes of allocatable ram. Not many desktop > machines > > > > have so much, so I'm stuttering along on virtual memory which makes > it > > > > slow. (It's been busy for 2 hours already) > > > > > > But it does feel strange to me that gwtc would need so much ram, > which > > > > is why I'm asking if we can work with the compiler in this case to > > > > keep these requirements down. The other option is that we are doing > > > > something wrong (which is slightly more likely). Maybe somebody can > > > > help us sort it out? > > > > > > Pieter > > > > > > On Jan 25, 11:59 am, Francisco Bischoff <[email protected]> > > > > wrote: > > > > > Hi, > > > > > > > I'm not the very experient here, but have you tried to follow the > > > > compiler > > > > > error? > > > > > > > [ERROR] Out of memory; to increase the amount of memory, use the > -Xmx > > > > flag > > > > > at startup (java -Xmx128M ...) > > > > > > > Maybe you just need to reserve more memory for the java compiler. > > > > > > > -- > > > > > Francisco Bischoffhttp://www.cirurgiaplastica.pro.br > > > > > > > "O mate está para o gaúcho como o chá para os ingleses, a coca para > os > > > > > bolivianos, o uísque para os escoceses e o café... para os > brasileiros" > > > > > -- Eduardo Bueno > > > > > > > On Mon, Jan 25, 2010 at 9:47 AM, Pieter Breed < > [email protected] > > > > >wrote: > > > > > > > > [ERROR] Out of memory; to increase the amount of memory, use > > > > > > the -Xmx flag at startup (java -Xmx128M ...) > > > > > > -- > > > > 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]<google-web-toolkit%[email protected]><google-web-toolkit%2Bunsubs > [email protected]> > > > > . > > > > For more options, visit this group at > > > >http://groups.google.com/group/google-web-toolkit?hl=en. > > -- > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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.
