This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Error While generating Model Reports | ||
---|---|---|---|
Product: | contrib | Reporter: | sajeevvarghese <sajeevvarghese> |
Component: | Jackpot | Assignee: | issues@contrib <issues> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | ||
Priority: | P4 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Error Log |
Description
sajeevvarghese
2006-07-13 09:32:07 UTC
Created attachment 31804 [details]
Error Log
First, this issue has nothing to do with Jackpot, as your system doesn't have any of its modules installed. More importantly, each failure in your log has the following line: Caused by: java.lang.OutOfMemoryError: Java heap space It appears that your IDE needs a higher maximum memory setting, either because you have so many modules installed or because the UML reporter is being run with a large project. In any case, edit the <NetBeans-installation-dir>/etc/netbeans.conf file and change its -Xmx128m flag (which sets the maximum JVM memory to 128 meg) to a higher value. If you have a lot of memory (more than 512 mb) trying doubling that value to 256m or moreDon't allocate so much memory that your system starts using virtual memory, however, as that will hurt performance. |