Out of memory error in ant

Question

I am trying to run ant task, however I get the following error:

[javadoc] javadoc: error - java.lang.OutOfMemoryError: Please increase memory.
[javadoc] For example, on the Sun Classic or HotSpot VMs, add the option -J-Xmx
[javadoc] such as -J-Xmx32m.
[javadoc] 1 error
[javadoc] 103 warnings

I have tried googling to find out how I can set this value, but I cannot find it. I have tried

<javadoc maxmemory="256m">

I have tried

export ANT_OPTS=-Xmx256m

but I still get the same exception. I have tried to increase the value to 1024m witouth any success

Update

I solved it. It had nothing to do with little memory. It was an endeless loop in my javadoc generation.

You seem to be missing the recommended -J in your export. – dlamblin Jan 06 '11 at 18:44 — dlamblin, Jan 06 '11 at 18:44

score 13 · Accepted Answer · edited Mar 20 '17 at 10:04

13

I solved it.

It had nothing to do with little memory. It was an endeless loop in my javadoc generation.

The correct way of setting more memory for ant is by using export ANT_OPTS=-Xmx256m on *nix.

On Windows follow the usual steps for setting environment variables.

edited Mar 20 '17 at 10:04

Community

1
1

answered Jan 07 '11 at 14:34

Shervin Asgari

23,901
30
103
143

2

Hi How did you find out that there is endless loop ?. I am facing similar issue while dexing the classes. – Shakti Malik Jan 31 '13 at 20:37
There was an endlees loop in the code we had where we where generating javadoc. – Shervin Asgari Feb 06 '13 at 16:50
Can you please elaborate ? The loop was between javadoc references ? If so, how can you get more info about the loop itself, how can one trace that loop ? – Patrice M. Jun 24 '14 at 17:44
The loop was in our code that generated the javadoc – Shervin Asgari Jun 25 '14 at 12:25

score 6 · Answer 2 · answered Jan 06 '11 at 18:45

6

The javac ant task has the attribute memoryMaximumSize which you should set to the same value as you would for -Xmx.

<javac memoryMaximumSize="256m" ...>
  ...
</javac>

I should add that this assumes that it is indeed a javac task that's causing the memory overrun.

answered Jan 06 '11 at 18:45

Mike Yockey

4,565
22
41

Was it the same behavior because the amount of memory didn't change where you needed it or did you not allocate enough memory? Bear in mind too that changing the max memory size can affect the sizes of the heap and the stack differently. Increasing the amount of memory may actually result in a smaller stack or heap in some instances. Some experimentation will be necessary. – Mike Yockey Jan 07 '11 at 14:38
2

The above option must be combined with fork="true" to work. This will run javac in a separate process with its own heap size settings. This will also limit any memory leaks in javac implementation to its own child process, without affecting the parent Ant process. – zkarthik Jul 23 '13 at 17:58

Out of memory error in ant

2 Answers2

Linked