Memory consumption exceeds default JVM tolerance

[GoogleCodeExporter]

What steps will reproduce the problem?
1. mvn clean site

What is the expected output? What do you see instead?
- Expect to see report generated.  Instead the process runs for a long
time, and quits with OOM:

WARNING: class not found: ####CENSORED BY SUBMITTER####
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Java heap space
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.OutOfMemoryError: Java heap space
        at org.objectweb.asm.ClassReader.a(Unknown Source)
        at org.objectweb.asm.ClassReader.<init>(Unknown Source)
        at
com.google.test.metric.JavaClassRepository.parseClass(JavaClassRepository.java:7
5)
        at
com.google.test.metric.JavaClassRepository.getClass(JavaClassRepository.java:47)
        at
com.google.test.metric.TestabilityVisitor$Frame.recordMethodCall(TestabilityVisi
tor.java:359)
        at
com.google.test.metric.method.op.turing.MethodInvokation.visit(MethodInvokation.
java:67)
        at
com.google.test.metric.TestabilityVisitor$Frame.applyMethodOperations(Testabilit
yVisitor.java:332)
        at
com.google.test.metric.TestabilityVisitor$CostRecordingFrame.applyMethodOperatio
ns(TestabilityVisitor.java:15
6)
        at
com.google.test.metric.MetricComputer.compute(MetricComputer.java:85)
        at
com.google.test.metric.MetricComputer.compute(MetricComputer.java:56)
        at
com.google.test.metric.JavaTestabilityRunner.run(JavaTestabilityRunner.java:77)
        at
com.google.maven.TestabilityExplorerMojo.executeReport(TestabilityExplorerMojo.j
ava:188)
        at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java
:98)


What version of the product are you using? On what operating system?
- 1.3.1-SNAPSHOT, Windows XP


Please provide any additional information below.
- I was able to work around the problem by adding MAVEN_OPTS=-Xmx1g

Original issue reported on code.google.com by pedro....@gmail.com on 29 Apr 2009 at 6:02

[GoogleCodeExporter]

Using MAVEN_OPTS is a typical need for more than small code bases.  I don't 
think
this issue is a bug, unless I misunderstand your report.

Original comment by jeffjjen...@gmail.com on 24 Feb 2010 at 8:20

[GoogleCodeExporter]

I think you understood fine.  Basically, the user experience for the 1st timer 
is this:

1. download testability explorer
2. modify pom.xml of my project
3. run "mvn clean site"
4. maven spins for a long time and blows up with OOM.
5. ...
6. Profit.

Original comment by pedro....@gmail.com on 24 Feb 2010 at 8:26

[GoogleCodeExporter]

OK... perhaps then a "getting started" page with:
  For Maven users:
   1. Add the following dep to reporting section...
   2. Since TE requires a lot of resources, may need to set MAVEN_OPTS=-Xmx1024m
   3. Run "mvn clean site".

No need for download anymore, as 1.3.3 is in central! :-)

Original comment by jeffjjen...@gmail.com on 24 Feb 2010 at 9:06

[GoogleCodeExporter]

That'd be great. :)

Original comment by pedro....@gmail.com on 24 Feb 2010 at 9:07