To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=77241
------- Additional comments from [EMAIL PROTECTED] Mon May 14 08:19:36 +0000 2007 ------- This issue has to do with the huge amount of data the engine has to generate. Our current fix for that issue is to use some smarter buffering inside the engine, which greatly reduced the memory overhead and therefore allowed us to run large reports inside the defautl 64MB OpenOffice seems to assign to the JVM (and thus to the reporting engine). This change allowed me to successfully create a report from 8000 rows of data (resulting in a 145MB content.xml [about 760 pages]). The memory consumption is high, because the document's styles are computed while the content is generated, but they have to appear in their own section at the beginning of the 'content.xml'. And faced with the choice to either run the report twice (using the first run to compute the styles, and the second one to generate the document body) or to use buffering, we headed for the buffering. If guaranteed infinite size report processing is needed, and if it is impossible to grant us more than the default 64MB memory, we can always switch to the multi-pass reporting instead of the buffering. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
