Re: GWT Compilation Out Of Memory

2019-03-14 Thread Colin Alworth
Some quick observations from the docx: The bulk of your split points are sized pretty well, but if you can save the compiler work on those tiny ones and delete/merge them, that would be ideal, and may well help your leftovers. That leftovers is quite large, but not totally out of control at

Re: GWT Compilation Out Of Memory

2019-03-14 Thread Vineet Jaiswal
where as no. of code lines are concerned I can give you only an approx. figure. 1. client + shared there might be minimum 10,00,000 lines code approx. 2. server there might be minimum 50,000 lines code approx. -- You received this message because you are subscribed to the Google Groups

Re: GWT Compilation Out Of Memory

2019-03-14 Thread Vineet Jaiswal
please find all details asked by as word attachment & along with I am attaching sample code of client, server, shared as rar file -- 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,

Re: Unexpected behavior

2019-03-14 Thread Velusamy Velu
Colin: Appreciate that, and I got the solution I have been looking for in your response. On Thursday, March 14, 2019 at 8:48:09 AM UTC-4, Colin Alworth wrote: > > Also telling your JS debugger to pause on uncaught exceptions will help - > it will stop when that null.toString() takes place,

Re: GWT Compilation Out Of Memory

2019-03-14 Thread Colin Alworth
Are you able to answer the other questions too? This looks like the same numbers that was in your last email. "Lines of code" refers to the sources that the developers write, not the generated JS. My reply also asked for more detail on the deferredjs contents, just the last file numerically in

Re: GWT Compilation Out Of Memory

2019-03-14 Thread Vineet Jaiswal
folders & files size generated in war are as follows: 1. deferredjs folder contains 5 folders (441mb of js files cumulative) 2. *.gwt.rpc 647 files (308mb cumulative) 3. *.cache.html 5 files (27.9mb cumulative) 4. *.nocache.js is 8kb 5. and other folders On Thu, Mar 14, 2019 at

Re: Unexpected behavior

2019-03-14 Thread Colin Alworth
Also telling your JS debugger to pause on uncaught exceptions will help - it will stop when that null.toString() takes place, letting you examine which method you are in when it happens, and which local variable or field is null. On Wednesday, March 13, 2019 at 3:33:48 PM UTC-5, Jens wrote: >

Re: GWT Compilation Out Of Memory

2019-03-14 Thread Colin Alworth
How much Java code goes into this? Combined file, line counts between shared and client packages? >From your .gwt.rpc files, My guess is that you have a huge amount of duplication between RPC interfaces. Improper use of supertypes, generics, interfaces, etc can cause the compiler to believe

Re: GWT Compilation Out Of Memory

2019-03-14 Thread Frank
How 'large' is your application ? How many lines of code ? How many screens ? I can't imagine that a war file of 1.6GB is normal ? (unless it contains heeps of images/multimedia assets) -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To

Re: GWT Compilation Out Of Memory

2019-03-14 Thread Vineet Jaiswal
1. is there any relation between split points & *.cache.html files. 2. what should be the supposed ideal time of compilation for my application. as I have mentioned the size of war generated after compilation & keeping the system configuration in mind. folders & files size generated in war

GWT Compilation Out Of Memory

2019-03-14 Thread Vineet Jaiswal
GWT version: 2.6.1 Browser (with version): any Operating System: Windows -- My Application is producing 1.6GB of war file and taking 7 to 8 hrs. for complete build of 5 permutation. configuration of machine on which we are compiling is: OS: windows server 2012 R2