[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-15398 at 9/16/13 7:38 PM: ------------------------------------------------------------------------ I run clean/build of wildly workspace on Eclipse with Maven 1.5.0 (link above). When run with 1Gb memory, build stuck at 83%, memory usage is shown in !MemoryUsedWithNewMaven.png|thumbnail! Maybe new Maven does not have memory leak now, and releases memory, but it uses it a lot while building. I had to kill Eclipse. When run with 1.5Gb, build stuck at 100%, I had to kill Eclipse again. When run with 1.8Gb, build passed in 10 minutes, on the verge of memory. I did a few modifications on files, then clean build on a few projects. After that I might believe that Maven released some memory used in build of workspace. Memory usage after all builds were completed is shown in !MemoryUsedWithNewMavenAfterBuild.png|thumbnail! It seems that Maven still keeps all grabbed memory. My general impression is that Maven 1.5 takes *more* memory than Maven 1.4. With maven 1.4 I was able to do clean/build of wildfly workspace in 5 minutes. was (Author: scabanovich): I run clean/build of wildly workspace on Eclipse with Maven 1.5.0 (link above). When run with 1Gb memory, build stuck at 83%, memory usage is shown in !MemoryUsedWithNewMaven.png|thumbnail! Maybe new Maven does not have memory leak now, and releases memory, but it uses it a lot while building. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira