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 28283] - OutOfMemory error
Date Wed, 13 Sep 2006 14:56:59 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28283>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=28283





------- Additional Comments From gudnabrsam@yahoo.com  2006-09-13 14:56 -------
(In reply to comment #6)
> The copy task does use a lot of memory.
> It keeps all the file names in memory, and for
> each file it has a list of target files.map(string->list)
> (This has changed from 1.5 to 1.6 files.map(string->string)).
> {or something similar}.
> This does not scale for large number of files.
> To handle large number of files, one needs a copy task
> that is implemented like an iterator - does one input file
> at a time and moves to the next input file.
> 

Right, I should have said that the implementation might be less than optimal. 
However, I wouldn't call it buggy.  In the case of <move> the mapping is IMO
definitely necessary as it allows to determine whether the <move> applies to an
entire directory tree so that the actual move process is much less complicated.
 For <copy> I can't think why we couldn't do 1 file at a time, but we would
probably need to cull duplicates first.  This might still be time and/or
memory-intensive... :|


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message