This doesn't address code-splitting per-se, but r8921 and r8850 reduce both
DevMode and compiler memory footprint.

On Sat, Sep 18, 2010 at 11:34 PM, lin.liang <birdandfis...@gmail.com> wrote:

> Chris, I didn't see the OOME before using code splitting. In order to
> reduce the application's startup time, I adopt code splitting in the
> DynaClassGenerator.java (the implementation of GWT generator on data
> deferred binding in our project)
>
> 1) Before using code splitting, the code is:
>    if
>
> ("com.nantian.iwap3.frameworkdev.client.dataitem.DataItemMgr".equals(className))
> {
>       ....
>       com.nantian.iwap3.frameworkdev.client.dataitem.DataItemMgr
> instance = new
>
> com.nantian.iwap3.frameworkdev.client.dataitem.DataItemMgr();
>       ....
>    }
>
> 2) After using code splitting:
>      if
>
> ("com.nantian.iwap3.frameworkdev.client.dataitem.DataItemMgr".equals(className))
> {
>       ....
>      GWT.runAsync(new RunAsyncCallbackAdapter() {
>         public void onSuccess() {
>            com.nantian.iwap3.frameworkdev.client.dataitem.DataItemMgr
> instance = new
> com.nantian.iwap3.frameworkdev.client.dataitem.DataItemMgr();
>            callback.onSuccess((T)instance);
>         }
>      });
>       ....
>    }
>
> In the former one, the complier work fine. However, in the second one,
> the complie process was interrupted by the OOME.
> P.S. It about 1,000 instances created by this way (e.g.
> com.nantian.iwap3.frameworkdev.client.dataitem.DataItemMgr above).
>
>
> On 9月17日, 下午11时00分, Chris Conroy <con...@google.com> wrote:
> > That should be more than enough memory to run your compile. Do you have a
> > stack trace for the OOME?
> >
> > FWIW, I have a pending change that should decrease the amount of memory
> > needed to run a compile or DevMode.
> >
> >
> >
> > On Fri, Sep 17, 2010 at 7:19 AM, lin.liang <birdandfis...@gmail.com>
> wrote:
> > > The OutOfMemory exception always happen when the gwt project was
> > > complied. The gwt project has 7 modules, and about 5,700 java files.
> >
> > > I have a look at gwt docs. It said that when the project became
> > > bigger, the complier using the memory more too. However, I have set
> > > the memory to 1.7G, it still report the OutOfMemory exception. Is this
> > > the bug of gwt complier? How can I do to solve this issue?
> >
> > > I have no clue about this so far. Look forward your response. Thanks!
> >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Google Web Toolkit" group.
> > > To post to this group, send email to
> google-web-tool...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com>
> <google-web-toolkit%2bunsubs-cr...@googlegroups.com<google-web-toolkit%252bunsubs-cr...@googlegroups.com>
> >
> > > .
> > > 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 google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to