Hi Aaron, Did you ever find a way to make this work? I'm running in to the same problem. I have an app that currently compiles to about 12mb of javascript, but that single large file is killing my load times on IE. I tried splitting it at my most logical spots, which causes about 100 split points. When I have just a few splits, it works fine. But when I try to do the full splitting, the compile takes an order of magnitude longer and usually blows the heap space before it finishes.
This is on some relatively small hardware, but I'm giving the compiler 3gb of memory to work with and limiting it to a single localWorker thread. Without the split points, I can compile it with just over 1gb of memory. Thanks, Eric -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/eSlVbErXj14J. To post to this group, send email to google-web-toolkit@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.
