y, October 06, 2009 8:36 PM
To: Ant Users List
Subject: Re: Out of memory
> -Xms128m -Xmx768m -XX:MaxPermSize=512m -XX:+UseConcMarkSweepGC
>
> -Xms should be set to 1/64 of your memory size, -Xmx should be set
> to 1/4 as a max
How did you
-Xms128m -Xmx768m -XX:MaxPermSize=512m -XX:+UseConcMarkSweepGC
-Xms should be set to 1/64 of your memory size, -Xmx should be set
to 1/4 as a max
How did you arrive at these "rules"?
-
To unsubscribe, e-mail: user-un
On 2009-10-06, Knuplesch, Juergen wrote:
> It happened this time (I earlier had to increase the memory) in the
> non standard pack200 Task:
> D:\DopeBuildBase\Build\DopeBuildServer\dopebuildwar.xml:356:
> java.lang.OutOfMemoryError
> This task made also a few problems, when I used it first. I
e.org]
Gesendet: Dienstag, 6. Oktober 2009 11:59
An: user@ant.apache.org
Betreff: Re: Out of memory
On 2009-10-06, Knuplesch, Juergen wrote:
> Hello,
> Thanks for your answer!
> Good to know, that there are known problems.
Unfortunately they may not be.
> I already fork the junit
On 2009-10-06, Knuplesch, Juergen wrote:
> Hello,
> Thanks for your answer!
> Good to know, that there are known problems.
Unfortunately they may not be.
> I already fork the junit tests.
Then the change I pointed at won't affect you since the classloader leak
only applies to non-forked tests
On 2009-10-06, Knuplesch, Juergen wrote:
> My build runs now with -Xmx1500m and still out of memory.
> It seems that the memory of big tasks I use is not garbage collected
> after I used them. (e.g. XSLT with saxon on the classpath, junit with
> 2200 tests...)
Ant 1.7.1 has a few classloader l
Knuplesch wrote:
In my Ant file the junitreport Task runs out of memory!
Where is the best place to increase the memory?
1. set ANT_OPTS environment variable to something like -Xmx512M
2. drop a copy of xalan (from xml.apache.org) into ANT_HOME/lib. This
XSL engine consumes less memory than
Google "ANT_OPTS"
--
Jeffrey E. Care ([EMAIL PROTECTED])
WebSphere v7 Release Engineer
WebSphere Build Tooling Lead (Project Mantis)
Mark McKay <[EMAIL PROTECTED]> wrote on 10/15/2005 08:36:52 AM:
> I'm getting OutOfMemoryErrors while running a task that uses the
> ProGuard ant task. This is
oman
>
> > -Ursprüngliche Nachricht-
> > Von: Ivan Ivanov [mailto:[EMAIL PROTECTED]
> > Gesendet: Donnerstag, 21. April 2005 11:53
> > An: Ant Users List
> > Betreff: Re: Out of Memory Error
> >
> > Good Morning Roman
> > --- Huditsch Roman <[E
Good Morning Roman
--- Huditsch Roman <[EMAIL PROTECTED]>
wrote:
> Good morning list,
>
> I encountered a slight problem, when doing my xslt
> transformations by an
> ant build file.
> It seems that I am running out of memory.
> Do can I give ant a bigger share of my memory?
Yes, you can use ANT_O
Darin:
Can you isolate a particular java program that causes this out of memory
exception? Are there a lot of files to troubleshoot?
Mani
-Original Message-
From: Darin Swanson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 25, 2004 4:09 PM
To: Ant Users List
Subject: RE: Out of memory
25/2004 12:37 PM
Please respond to "Ant Users List"
To: "Ant Users List" <[EMAIL PROTECTED]>
cc:
Subject:RE: Out of memory with javac
Hi Darin.
I don't have your answer however I'm curious if your problem works fine on
1
: Ant Users List
Subject: RE: Out of memory with javac
Thanks NetaB...but I don't think you helped me at all :-)
I have fork set to be true so memorymaximumsize and memoryinitialsize
should not be ignored.
The main thrust of my question is why the difference running on the two
implementat
work on 1.4.2?
I could not find a bug in Sun's bug parade either for this problem with
javac.
TIA
Darins
"Neta Bar Tal" <[EMAIL PROTECTED]>
05/24/2004 09:21 PM
Please respond to "Ant Users List"
To: "Ant Users List" <[EMAIL PROTECTED]
14 matches
Mail list logo