ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 25394] - OutofMemory when running lots of <script> tasks
Date Tue, 23 Dec 2003 15:52:26 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25394>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25394

OutofMemory when running lots of <script> tasks

peter.reilly@corvil.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From peter.reilly@corvil.com  2003-12-23 15:52 -------
I do not think so.
There is no need to set fields in a object to
null - if the object itself is garbage collected....
oh, oh...................... penny drops.....

Antonie, you are correct........
The script task object is referenced by the wrapper pointer
in RuntimeConfigurable, the RuntimeConfigurable object is referenced
by the UnknownElement, the UnknownElement is referenced by its
parent and it by the target and it by the project.

So tasks in ant are created and never GC'ed - not good.

Actually the live-cycle of a Task is not well documented so simply
setting the scriptrunner to null is not good as the execute
may be called twice.

In any case, a simple change like Antoine's should solve
this particular problem.

I have updated ant HEAD and ant 1.6 HEAD

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


Mime
View raw message