You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jörg Hohwiller (JIRA)" <ji...@codehaus.org> on 2013/10/22 00:40:52 UTC

[jira] (MJAVADOC-308) OutOfMemoryError

     [ https://jira.codehaus.org/browse/MJAVADOC-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jörg Hohwiller updated MJAVADOC-308:
------------------------------------

    Attachment: java7-javadoc-memorybug.png

sorry for spamming this issue but Oracle just like sun does not allow transparent and open bug reporting for Java.
I attached a screenshot of jvisualvm showing a heap histogram of the javadoc process when it died with 2GB of heap.
                
> OutOfMemoryError
> ----------------
>
>                 Key: MJAVADOC-308
>                 URL: https://jira.codehaus.org/browse/MJAVADOC-308
>             Project: Maven Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.6.1, 2.7
>         Environment: Maven 3 on MacOS 10.6, Maven 3 on Hudson on Windows
>            Reporter: Pieter
>         Attachments: java7-javadoc-memorybug.png
>
>
> I have a 12 module project (+parent) containing not really much code (140 classes). When running Maven site on this project, it fails with an OutOfMemoryError. When I run the javadoc plugin with a reportset containing javadoc, test-javadoc and aggregate is runs well with a maximum heap size of 512M. When I run it with a reportset containing javadoc, test-javadoc and test-aggregate also. But when I add all 4 reports to my report set, I get an OutOfMemoryError, even when setting the maximum heap size to 1.5G. Just before the error occurs I see my heap usage growing rapidly.

--
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