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 20264] New: - Memory leak when using ExecuteJava
Date Tue, 27 May 2003 14:40:04 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=20264>.
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=20264

Memory leak when using ExecuteJava

           Summary: Memory leak when using ExecuteJava
           Product: Ant
           Version: 1.5.3
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core
        AssignedTo: dev@ant.apache.org
        ReportedBy: shaul@comsoft.co.il


I've written a small task that run a java program using ExecuteJava during the 
build process.  After a clean build this task is calls the ExecuteJava.execute 
more than 200 times.

When ExecuteJava finish each time it is calling the AntClassLoader.cleanup() 
method.  Calling the cleanup() method don't remove the instance of 
AntClassLoader from the project using "project.removeBuildListener(this);".
I couldn't find any other method that will properly remove that reference.

Memory leak from AntClassLoader is an old bug that it is currently resolved - 
you can see it at http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8689
but the resolution isn't working for ExecuteJava.

Mime
View raw message