cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: [FIXED] Re: Build system problems on OS/X 10.2.3, Linux andWindows
Date Thu, 09 Jan 2003 07:36:06 GMT

David Crossley wrote:
>
> Ovidiu Predescu wrote:
> > Sylvain Wallez wrote:
> > > Ovidiu Predescu wrote:
> > >
> > >> By increasing the amount of heap space allocated to the JVM, the
> > >> build works fine now. I've added the -Xmx512mb parameter to the java
> > >> invocation in tools/bin/ant, the last line in this file. A similar
> > >> thing has to be done in tools/bin/ant.bat. I can check-in
> this change
> > >> if it fixes the build problem for everybody that has it.
> > >
> > > Any idea of why the 2.1 build needs so much memory when 2.0 builds
> > > fine with the default options ?
> >
> > I just put some size, I don't think that's the right value. Who knows,
> > maybe the build crashes because the JVM cannot allocate 1Mb over the
> > default size, whichever that is. I just wanted to have something
> > working so I put the amount of physical memory available on my laptop
> > ;) If you find that a lower value works, let's use that one.
>
> Whatever value is the default was working well until
> recently, when it just started crashing.
>
> > On my system, the build crashes while doing validation. Is it possible
> > that this step eats a lot of memory?
>
> The build crashes at completely different places for
> different people (please see the earlier thread).
> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=104138910730772
>
> It still crashes for me with today's CVS, this time
> during the "lucene-block" target.
>
> Your sledgehammer approach of "give it more heap-space"
> did succeed. But that is a "workaround" not a "fix" and
> CVS is still busted. How will we ever find the real cause?
> It was introduced recently to CVS.
>
It might be that these problems are introduced by our sub-build routines
for the blocks. Perhaps the internal ant invocations used for the
blocks building do not release memory before the complete build is over?
Just a guess.

Carsten


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message