Matt Dew wrote:
> On Wed, Sep 29, 2010 at 9:41 AM, Younes Manton <youne...@gmail.com> wrote:
>> On Wed, Sep 29, 2010 at 2:25 AM, Jeremy Huddleston <jerem...@apple.com>
>> wrote:
>>> This change seems to be causing documentation to fail building on yuffie due
>>> to java running out of memory…
>>> http://tinderbox.x.org/builds/2010-09-22-0004/logs/libX11/#build
>>> I seem to recall other "OutOfMemory" errors being reported wrt documentation
>>> earlier, but I don't recall any resolution. Looking at fop, it looks like
>>> we can setup a FOP_OPTS environment variable with an appropriate -Xmx
>>> argument to be passed along to java. I just tested this on yuffie by adding
>>> the following to my tinderbox script, and it resolved my build failure:
>>> export FOP_OPTS="-Xmx2048m"
>>> Obviously setting the max VM size as 2G universally isn't the best solution.
>>> I also don't expect everyone to know about FOPS_OPTS either, so what is the
>>> best way to resolve this across modules?
>> It's not a terrible solution, it's not like you'll actually be using
>> 2G on any halfway sane jvm except when you need it, it's just an upper
>> bound.
>
> FWIW,
> libX11 is the largest document and I found that using
> export FOP_OPTS="-Xmx512m" was sufficient.
The new documents I autogenerate from the Compose data files have some very
large tables in, most especially the en_US.UTF-8 compose key list - I'd set them
to split into new tables after 750 lines since that solved the java
out-of-memory issues in my environment, but it appears not to solve it for
everyone - the script can be adjusted to split at a different threshold if
that's easier than trying to find a way to set FOP_OPTS in the Makefile.am's.
--
-Alan Coopersmith- alan.coopersm...@oracle.com
Oracle Solaris Platform Engineering: X Window System
_______________________________________________
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel
