You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Nicolas Cazottes (JIRA)" <ji...@codehaus.org> on 2007/06/27 09:23:13 UTC
[jira] Created: (MNG-3073) Memory Leak in maven2 for multiproject
Memory Leak in maven2 for multiproject
--------------------------------------
Key: MNG-3073
URL: http://jira.codehaus.org/browse/MNG-3073
Project: Maven 2
Issue Type: Bug
Components: General, Performance
Affects Versions: 2.0.7
Reporter: Nicolas Cazottes
We use Maven2 for a massive multiproject composed of 433 jars projects in 3 levels of hierarchy and lots of inter-dependencies.
Our project contains 3577 classes at this time but it is constantly growing.
As it grows, the number of projects increases and the number of versions of each project increases as well.
What we are faced to is that we constantly need to increase the memory size allowed to Maven.
With 433 projects and 3577 classes, we need the following memory parameters : -Xmx900m -Xms128m for our compilation with the following command line : mvn install -Dmaven.test.skip=true.
I think there are memory leak in Maven that explains this behaviour.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3073) Memory Leak in maven2 for multiproject
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-3073.
------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.2.x)
> Memory Leak in maven2 for multiproject
> --------------------------------------
>
> Key: MNG-3073
> URL: http://jira.codehaus.org/browse/MNG-3073
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: General, Performance
> Affects Versions: 2.0.7
> Reporter: Nicolas Cazottes
>
> We use Maven2 for a massive multiproject composed of 433 jars projects in 3 levels of hierarchy and lots of inter-dependencies.
> Our project contains 3577 classes at this time but it is constantly growing.
> As it grows, the number of projects increases and the number of versions of each project increases as well.
> What we are faced to is that we constantly need to increase the memory size allowed to Maven.
> With 433 projects and 3577 classes, we need the following memory parameters : -Xmx900m -Xms128m for our compilation with the following command line : mvn install -Dmaven.test.skip=true.
> I think there are memory leak in Maven that explains this behaviour.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3073) Memory Leak in maven2 for multiproject
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204475#action_204475 ]
Jason van Zyl commented on MNG-3073:
------------------------------------
Fixed in 3.x.
> Memory Leak in maven2 for multiproject
> --------------------------------------
>
> Key: MNG-3073
> URL: http://jira.codehaus.org/browse/MNG-3073
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: General, Performance
> Affects Versions: 2.0.7
> Reporter: Nicolas Cazottes
>
> We use Maven2 for a massive multiproject composed of 433 jars projects in 3 levels of hierarchy and lots of inter-dependencies.
> Our project contains 3577 classes at this time but it is constantly growing.
> As it grows, the number of projects increases and the number of versions of each project increases as well.
> What we are faced to is that we constantly need to increase the memory size allowed to Maven.
> With 433 projects and 3577 classes, we need the following memory parameters : -Xmx900m -Xms128m for our compilation with the following command line : mvn install -Dmaven.test.skip=true.
> I think there are memory leak in Maven that explains this behaviour.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3073) Memory Leak in maven2 for multiproject
Posted by "Milos Kleint (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100669 ]
Milos Kleint commented on MNG-3073:
-----------------------------------
forking the compiler could have influence on memory usage as well. Haven't measured rigorously though.
> Memory Leak in maven2 for multiproject
> --------------------------------------
>
> Key: MNG-3073
> URL: http://jira.codehaus.org/browse/MNG-3073
> Project: Maven 2
> Issue Type: Bug
> Components: General, Performance
> Affects Versions: 2.0.7
> Reporter: Nicolas Cazottes
>
> We use Maven2 for a massive multiproject composed of 433 jars projects in 3 levels of hierarchy and lots of inter-dependencies.
> Our project contains 3577 classes at this time but it is constantly growing.
> As it grows, the number of projects increases and the number of versions of each project increases as well.
> What we are faced to is that we constantly need to increase the memory size allowed to Maven.
> With 433 projects and 3577 classes, we need the following memory parameters : -Xmx900m -Xms128m for our compilation with the following command line : mvn install -Dmaven.test.skip=true.
> I think there are memory leak in Maven that explains this behaviour.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3073) Memory Leak in maven2 for multiproject
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3073:
------------------------------
Fix Version/s: 2.0.x
> Memory Leak in maven2 for multiproject
> --------------------------------------
>
> Key: MNG-3073
> URL: http://jira.codehaus.org/browse/MNG-3073
> Project: Maven 2
> Issue Type: Bug
> Components: General, Performance
> Affects Versions: 2.0.7
> Reporter: Nicolas Cazottes
> Fix For: 2.0.x
>
>
> We use Maven2 for a massive multiproject composed of 433 jars projects in 3 levels of hierarchy and lots of inter-dependencies.
> Our project contains 3577 classes at this time but it is constantly growing.
> As it grows, the number of projects increases and the number of versions of each project increases as well.
> What we are faced to is that we constantly need to increase the memory size allowed to Maven.
> With 433 projects and 3577 classes, we need the following memory parameters : -Xmx900m -Xms128m for our compilation with the following command line : mvn install -Dmaven.test.skip=true.
> I think there are memory leak in Maven that explains this behaviour.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3073) Memory Leak in maven2 for multiproject
Posted by "Nicolas Cazottes (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100688 ]
Nicolas Cazottes commented on MNG-3073:
---------------------------------------
I actually set the memory configuration I mentionned through the environment variable MAVEN_OPTS.
My point is that the solution to increase the memory endless is not a good one because I may be at some time faced to a limit of my computer memory size if my number of projects increases to 1000.
Forking the compiler should be an option but I think it will increase the compilation time which is currently 12min average. I will try it to see.
> Memory Leak in maven2 for multiproject
> --------------------------------------
>
> Key: MNG-3073
> URL: http://jira.codehaus.org/browse/MNG-3073
> Project: Maven 2
> Issue Type: Bug
> Components: General, Performance
> Affects Versions: 2.0.7
> Reporter: Nicolas Cazottes
>
> We use Maven2 for a massive multiproject composed of 433 jars projects in 3 levels of hierarchy and lots of inter-dependencies.
> Our project contains 3577 classes at this time but it is constantly growing.
> As it grows, the number of projects increases and the number of versions of each project increases as well.
> What we are faced to is that we constantly need to increase the memory size allowed to Maven.
> With 433 projects and 3577 classes, we need the following memory parameters : -Xmx900m -Xms128m for our compilation with the following command line : mvn install -Dmaven.test.skip=true.
> I think there are memory leak in Maven that explains this behaviour.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MNG-3073) Memory Leak in maven2 for
multiproject
Posted by "Debabrat (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100667 ]
Debabrat edited comment on MNG-3073 at 6/27/07 3:01 AM:
--------------------------------------------------------
Set the memory size inside "Maven2.0.4/bin/mvn.bat" file
like this set ANT_OPTS= -Xmx1024m
for your reference where to set ANT_OPTS
@REM Reaching here means variables are defined and arguments have been captured
:endInit
SET MAVEN_JAVA_EXE="%JAVA_HOME%\bin\java.exe"
set ANT_OPTS= -Xmx1024m
was:
set your memery size inside mvn.bat file
like this set ANT_OPTS= -Xmx1024m
for your reference
@REM Reaching here means variables are defined and arguments have been captured
:endInit
SET MAVEN_JAVA_EXE="%JAVA_HOME%\bin\java.exe"
set ANT_OPTS= -Xmx1024m
> Memory Leak in maven2 for multiproject
> --------------------------------------
>
> Key: MNG-3073
> URL: http://jira.codehaus.org/browse/MNG-3073
> Project: Maven 2
> Issue Type: Bug
> Components: General, Performance
> Affects Versions: 2.0.7
> Reporter: Nicolas Cazottes
>
> We use Maven2 for a massive multiproject composed of 433 jars projects in 3 levels of hierarchy and lots of inter-dependencies.
> Our project contains 3577 classes at this time but it is constantly growing.
> As it grows, the number of projects increases and the number of versions of each project increases as well.
> What we are faced to is that we constantly need to increase the memory size allowed to Maven.
> With 433 projects and 3577 classes, we need the following memory parameters : -Xmx900m -Xms128m for our compilation with the following command line : mvn install -Dmaven.test.skip=true.
> I think there are memory leak in Maven that explains this behaviour.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3073) Memory Leak in maven2 for multiproject
Posted by "Debabrat (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100667 ]
Debabrat commented on MNG-3073:
-------------------------------
set your memery size inside mvn.bat file
like this set ANT_OPTS= -Xmx1024m
for your reference
@REM Reaching here means variables are defined and arguments have been captured
:endInit
SET MAVEN_JAVA_EXE="%JAVA_HOME%\bin\java.exe"
set ANT_OPTS= -Xmx1024m
> Memory Leak in maven2 for multiproject
> --------------------------------------
>
> Key: MNG-3073
> URL: http://jira.codehaus.org/browse/MNG-3073
> Project: Maven 2
> Issue Type: Bug
> Components: General, Performance
> Affects Versions: 2.0.7
> Reporter: Nicolas Cazottes
>
> We use Maven2 for a massive multiproject composed of 433 jars projects in 3 levels of hierarchy and lots of inter-dependencies.
> Our project contains 3577 classes at this time but it is constantly growing.
> As it grows, the number of projects increases and the number of versions of each project increases as well.
> What we are faced to is that we constantly need to increase the memory size allowed to Maven.
> With 433 projects and 3577 classes, we need the following memory parameters : -Xmx900m -Xms128m for our compilation with the following command line : mvn install -Dmaven.test.skip=true.
> I think there are memory leak in Maven that explains this behaviour.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira