https://issues.apache.org/bugzilla/show_bug.cgi?id=49021
Summary: TaskDef/ScriptDef in Sub Build = Memory Disaster
Product: Ant
Version: 1.8.0
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: Core tasks
AssignedTo: [email protected]
ReportedBy: [email protected]
Sub-builds (antcall, subant) load a task each time the task is defined, but do
not release it when the sub-build project completes.
It would be best if the sub-build would recognize the task is already loaded,
just like it does when the task is loaded within the same project using
loaderref. If it is not feasible to re-use the task in this scenario, then it
should be released to avoid sucking up all the available memory very quickly. I
think this is only a problem with recent (> 1.5.8) releases of Groovy, since it
requires so much PermGen. You can't give it enough anymore.
The attached script runs out of memory in about 34 iterations of defining the
groovy task within an antcall.
It can be run as follows, where 3rdparty_libdir is the folder that contains the
jars needed for the groovy task:
ant -f GroovyMem.xml -Diterations=100 -D3rdparty_libdir=\3rdPartyJars\lib
Note: The script uses AntContrib to iterate.
http://marc.info/?l=ant-user&m=126970939205980&w=2
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
