You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2007/06/27 00:10:17 UTC
DO NOT REPLY [Bug 42742] - big Ant/Ivy builds run out of permanent memory. Classloader leaks?
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=42742>.
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=42742
------- Additional Comments From stevel@apache.org 2007-06-26 15:10 -------
Note for the curious that the jira bugrep includes a heap dump that you can use
java6;s jhat against (
http://jira.smartfrog.org/jira/secure/attachment/10030/java_pid1292.julio.zip )
If you look at the list of classes that are leaking, its the custom tasks that
are being taskdef'd, in particular ivy, primarily because its so big (once jhat
is running, the url is http://localhost:7000/allInstances/0x6ae5d00).
I'm loading these using typedef, rather than antlib uris, because each task is
designed to be self contained. I may be able to go back and skip the loading if
they are already on the classpath, but
1. we could maybe make this an option (reload=true/false) to check before loading
2. can't we stop loading so many instances? Surely when we exit a project, its
gone.
--
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
Re: DO NOT REPLY [Bug 42742] - big Ant/Ivy builds run out of permanent
memory. Classloader leaks?
Posted by Steve Loughran <st...@apache.org>.
bugzilla@apache.org wrote:
> 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=42742>.
> 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=42742
>
>
>
>
>
> ------- Additional Comments From stevel@apache.org 2007-06-26 15:10 -------
> Note for the curious that the jira bugrep includes a heap dump that you can use
> java6;s jhat against (
> http://jira.smartfrog.org/jira/secure/attachment/10030/java_pid1292.julio.zip )
>
> If you look at the list of classes that are leaking, its the custom tasks that
> are being taskdef'd, in particular ivy, primarily because its so big (once jhat
> is running, the url is http://localhost:7000/allInstances/0x6ae5d00).
>
> I'm loading these using typedef, rather than antlib uris, because each task is
> designed to be self contained. I may be able to go back and skip the loading if
> they are already on the classpath, but
> 1. we could maybe make this an option (reload=true/false) to check before loading
> 2. can't we stop loading so many instances? Surely when we exit a project, its
> gone.
>
I'm just following up with the note that this is a problem, that ivy
amplifies (its a big program). When we go <subant>, I'd really like all
tasks loaded in one sub project to be cleaned up before we move to the
next one. Any ideas?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org