There's nothing that special about MY stack trace... just run javac on a
largish module with a tiny heap.
(Our module was huge enough to fail with 800 megs, but there are plenty modules
that will fail with 8 megs, let alone one meg.)
Further, the exact stack trace is very sensitive to the exact
>> How can I can find out EXACTLY how maven invoked javac, so I can
>> invoke it the same way?
I think, somebody already mentioned earlier that you can just activate
debug output in Maven. Then search for the line following "Command line
options":
$ mvn -X compile | grep --after-context 1
Okay, I think I got it. Here is the error I get when running with -J-Xmx800
The system is out of resources.
Consult the following stack trace for details.
java.lang.OutOfMemoryError: GC overhead limit exceeded
-Original Message-
From: mark.yagnatin...@barclays.com.INVALID
Sent:
How can I can find out EXACTLY how maven invoked javac, so I can invoke it the
same way?
(While I await your response, I'll attempt to invoke it roughly the same way
and see if that works.)
-Original Message-
From: Alexander Kriegisch
Sent: Thursday, December 21, 2023 8:45 PM
To:
