[Bug 42742] big Ant/Ivy builds run out of permanent memory. Classloader leaks?

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=42742

kahmyong.moon@hp.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kahmyong.moon@hp.com

--- Comment #18 from kahmyong.moon@hp.com ---
I don't know if there's been any recent action on this, but after hitting a
similar issue (with Ant 1.7.2 through 1.9.2, and Ivy 2.3.0), and poking around
heap dumps for a while, I've noticed two potential issues:

1. On the Ant side, IntrospectionHelper.bean holds a reference to the Ivy
classes. Bug 30162 fixed a similar issue with embedded Ants by calling
IntrospectionHelper.clearCache() at the end of a build, but this doesn't cover
sub-builds.

2. On the Ivy side, IvyContext.getContext() automatically pushes an IvyContext
if one does not already exist (Message.getLogger() seems to do this pretty
early). Since this automatic IvyContext doesn't follow the scoping rules
introduced in https://issues.apache.org/jira/browse/IVY-639, this means there's
one IvyContext left hanging around after the subbuild ends.

Anyway, I'll probably go with the forking workaround mentioned by others in
this thread, but it would be nice to get the root issues fixed...

-- 
You are receiving this mail because:
You are the assignee for the bug.