Alex,

Modifying the mxmlc jvm arguments did the trick.

Using "mxmlc jvmargs" in a google search found
http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7fd9.html
which lead to the answer.

Thanks for the help.

Justin


On Mon, Sep 19, 2016 at 1:13 AM, Alex Harui <aha...@adobe.com> wrote:

>
> On 9/18/16, 7:02 PM, "Justin Magnan" <justin.mag...@magnantech.com> wrote:
>
> >I am having trouble with a build, I was hoping someone can help.
> >
> >
> >This had me wondering if maybe ant was running out of memory, I looked at
> >setting ANT_OPTS=-Xmx2098M, this did nothing.
> >
> >I then searched the web and found a couple links saying if you get out of
> >memory issues you can try fork="yes" which we already do and set the
> >maxmemory attribute. I tried adding maxmemory="2096m" and this also did
> >nothing to improve the situation.
> >
> ><mxmlc fork="yes" maxmemory="2096m" file="./flex_src/insDev.mxml"
> >    output="./../${deployment}/WebContent/insDev_${buildnumber}.swf"
> >    actionscript-file-encoding="UTF-8"
> >    keep-generated-actionscript="false"
> >    debug="false"
> >    optimize="true">
> >
> >    <default-frame-rate>30</default-frame-rate>
> >    <load-config filename="./insdevcfg.xml"/>
> >    <source-path path-element="${FLEX_HOME}/frameworks" />
> >    <compiler.source-path path-element="./flex_src" />
> ></mxmlc>
> >
> >
> >Any thoughts?
>
> I think there are jvmargs you can set to give mxmlc more memory.
>
> Modules should help you in several ways, from reducing build times as well
> as load times.
>
>
> HTH,
> -Alex
>
>

Reply via email to