Well, I would say to connect a profiler to maven and see where is the memory leak.... I do recall someone reported a memory leak in the past for FM and mvn 2.1 or something like that, and was some bug deep inside some maven-core dependency, not much I could do on flexmojos side.
VELO On Jul 14, 6:32 am, Wim Deblauwe <[email protected]> wrote: > I have upgraded to Maven 3 and flex-mojos 4.0-beta-7. I now get > OutOfMemoryError: > > java.lang.OutOfMemoryError: GC overhead limit exceeded > at java.lang.StringBuilder.toString(StringBuilder.java:430) > at java.lang.StackTraceElement.toString(StackTraceElement.java:157) > at java.lang.String.valueOf(String.java:2826) > at java.lang.StringBuilder.append(StringBuilder.java:115) > at java.lang.Throwable.printStackTrace(Throwable.java:512) > at flex2.tools.PostLink.merge(PostLink.java:236) > at flex2.tools.PostLink.run(PostLink.java:113) > at flex2.linker.API.link(API.java:53) > at flex2.tools.Compiler.mxmlc(Compiler.java:295) > at flex2.tools.Mxmlc.mxmlc(Mxmlc.java:8) > at > org.sonatype.flexmojos.compiler.DefaultFlexCompiler$2.command(DefaultFlexCompiler.java:59) > at > org.sonatype.flexmojos.compiler.command.CommandUtil$1.run(CommandUtil.java:33) > at java.lang.Thread.run(Thread.java:662) > > Is there something I can do to help debug this? > > regards, > > Wim -- You received this message because you are subscribed to the Google Groups "Flex Mojos" 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/flex-mojos http://flexmojos.sonatype.org/
