From issues-return-86771-apmail-maven-issues-archive=maven.apache.org@maven.apache.org Sun Sep 1 10:59:20 2013 Return-Path: X-Original-To: apmail-maven-issues-archive@minotaur.apache.org Delivered-To: apmail-maven-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5EB5B10182 for ; Sun, 1 Sep 2013 10:59:20 +0000 (UTC) Received: (qmail 24916 invoked by uid 500); 1 Sep 2013 10:59:19 -0000 Delivered-To: apmail-maven-issues-archive@maven.apache.org Received: (qmail 24833 invoked by uid 500); 1 Sep 2013 10:59:18 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 24825 invoked by uid 99); 1 Sep 2013 10:59:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Sep 2013 10:59:17 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [199.193.192.100] (HELO codehaus01.managed.contegix.com) (199.193.192.100) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Sep 2013 10:59:13 +0000 Received: from codehaus01 (localhost.localdomain [127.0.0.1]) by codehaus01.managed.contegix.com (Postfix) with ESMTP id B3BC0B10BE for ; Sun, 1 Sep 2013 05:58:52 -0500 (CDT) Date: Sun, 1 Sep 2013 05:58:52 -0500 (CDT) From: "Herve Boutemy (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] (MJAVADOC-308) OutOfMemoryError MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 22cf62d5d84cf5bea94eb3b65e0ebd09 X-Virus-Checked: Checked by ClamAV on apache.org [ https://jira.codehaus.org/browse/MJAVADOC-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332193#comment-332193 ] Herve Boutemy commented on MJAVADOC-308: ---------------------------------------- IMHO, you should try to run javadoc by hand: I don't really see how this can be a Maven bug causing OOME in javadoc, and what Maven Javadoc Plugin can do did you try configuring the plugin to give javadoc more memory? > 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 > > 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