Bad IvyContext scope causing memory leak and bad handling of subproject builds
------------------------------------------------------------------------------
Key: IVY-639
URL: https://issues.apache.org/jira/browse/IVY-639
Project: Ivy
Issue Type: Bug
Components: Core
Affects Versions: 2.0.0-alpha-2
Reporter: Xavier Hanin
Assignee: Xavier Hanin
Priority: Critical
Fix For: 2.0.0-beta-1
Ivy relies on a mechanism of IvyContext to access to some contextual
information without passing them throughout all methods parameters.
The problem is that only one context is attached to the current thread, and it
is never cleaned. This leads to two kind of problems:
- memory leak, which is the root cause of an issue reported in Ant:
http://issues.apache.org/bugzilla/show_bug.cgi?id=42742
- bad management of subprojects, in which the parent IvyContext is losed when
the subproject starts. Details about this have been reported by Peter Reilly:
http://www.nabble.com/use-of-IvyContext-tf4472787.html#a12752879
The solution to this problem is to use a stack of IvyContext rather than a
single one, and push the context on each Ivy method call, and pop it at the end.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
