Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Won't Fix
-
Affects Version/s: 1.0-JSR-2
-
Fix Version/s: None
-
Component/s: Ant integration
-
Labels:None
-
Environment:HideApache Ant version 1.6.1 compiled on February 12 2004
java version "1.4.2_08"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03)
Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)
or Eclipse 3.1 M5a with included ant and Java 1.5_02
Both running on Windows XP SP2ShowApache Ant version 1.6.1 compiled on February 12 2004 java version "1.4.2_08" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03) Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode) or Eclipse 3.1 M5a with included ant and Java 1.5_02 Both running on Windows XP SP2
-
Testcase included:yes
-
Number of attachments :
Description
There appears to be a memory leak in the groovy ant task. This becomes apparent when calling from one ant file to a number of others, each with a groovy task.
I performed the following tests:
- Increase the complexity and memory used of the groovy script in ant. This had no effect.
- Increase the number of groovy tasks in a single ant script. This had no effect
- Increase the total number of ant scripts called. This showed memory growth.
The following message is typical:
BUILD FAILED
D:\projects\config\build\temp\build.xml:13: Following error occured while executing this line
D:\projects\config\build\temp\dependencies.xml:87: Following error occured while executing this line
java.lang.OutOfMemoryError
I have attached a demonstration ant build system similar to our project build where the problem first occurred. For best results set the JVM memory via the ANT_OPTS environment variable to something like 16 Meg ie:
set ANT_OPTS=-Xmx16M
and then run ant.
Issue Links
- relates to
-
GROOVY-3656
Memory Leak in Groovy ant task
-