Yuk.
I've been using -Xms512m -Xmx1024m on Maven 2.2.1.
That looks like a bug in the JVM, perhaps. However, you aren't on the
latest release, which is 6.0_22, I think. Upgrade that first then see.
I haven't had any probs on 1.6_021.
What's the OS? I'm on Win7 64bit.
---
BTW, I also have started building on Maven 3.0. Seems to work fine so far.
It also has the option to build in parallel; when I did so I had to up
the memory (to -Xmx2048m). Running with 8 threads (2 per core) was a
bit faster, but not much (~20%). I guess I'm maxing out on the disks.
Dan
On 21/10/2010 19:41, Kevin Meyer - KMZ wrote:
What MAVEN_OPTS are you using to allow a successful "mvn clean
install" from trunk?
I've been nudging up the values, but I now get a:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at
pc=0x6d98c511, pid=1988, tid=1688
#
# JRE version: 6.0_17-b04
# Java VM: Java HotSpot(TM) Client VM (14.3-b01 mixed mode
windows-x86 )
# Problematic frame:
# V [jvm.dll+0xdc511]
#
# An error report file with more information is saved as:
# K:\Dev\NAKEDO~1\isis\trunk\hs_err_pid1988.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
