[
https://jira.codehaus.org/browse/MJAVADOC-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=334646#comment-334646
]
Jörg Hohwiller edited comment on MJAVADOC-308 at 10/25/13 1:37 PM:
-------------------------------------------------------------------
I spend more time on the analysis and think I traced it down now.
1. The problem does not occur with any heap size. If I use a 64 bit JVM and
provide 5GB of heap, the javadoc works. See the attached screenshot.
2. As I already wrote before the problem occurs when generating the
overview-tree.html. The implementation of this report in javadoc seems to be
very memory exhaustive (in java 1.7). IMHO the developers did not consider that
one may make intensive use of multi-inheritance via interfaces. My resulting
overview-tree.html is 241 megabytes big. My firefox is almost dying when I open
this file and scroll it. I never noticed this feature and do not need it. So
even though this is some sort of bug or problem in javadoc 1.7 I can switch it
off as a workaround:
http://docs.oracle.com/javase/1.5.0/docs/tooldocs/windows/javadoc.html#notree
http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#notree
3. If you omit the maximum heap size java 1.7 grows the heap more dynamically
if OS memory is available than java did in earlier versions. Therefore the
javadoc generation on a single module succeeded without max heap and failed
with -Xmx1024m.
Sorry for spamming. This bug is absolutely not related to the
maven-javadoc-plugin.
was (Author: hohwille):
I spend more time on the analysis and think I traced it down now.
1. The problem does not occur with any heap size. If I use a 64 bit JVM and
provide 5GB of heap, the javadoc works. See the attached screenshot.
2. As I already wrote before the problem occurs when generating the
overview-tree.html. I found out that this is a new feature of JavaDoc
introduced with java 1.7. That is why there are no problems with earlier java
versions.
The implementation of this report in javadoc seems to be very memory
exhaustive. IMHO the developers did not consider that one may make intensive
use of multi-inheritance via interfaces. My resulting overview-tree.html is 241
megabytes big. My firefox is almost dying when I open this file and scroll it.
I never noticed this feature and do not need it. Maybe there is an option to
disable it and all my problems are resolved.
3. If you omit the maximum heap size java 1.7 grows the heap more dynamically
if OS memory is available than java did in earlier versions. Therefore the
javadoc generation on a single module succeeded without max heap and failed
with -Xmx1024m.
> 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-5GB.png,
> java7-javadoc-memorybug-monitor.png, 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
