Created attachment 27849 [details]
Bugdoc

Adding SUS to CC

SUS->LO:
As discussed this easy document has a content.xml of 20 MB.

It has 21000 rows of 9 columns each, providing for each cell
<table:table-cell office:value-type="float"
office:value="3000"><text:p>3000</text:p></table:table-cell>
of about 100 characters results alone into
18 900 000 Characters..

This should still be parsable and even by a simpelst copy transformation Java
throws a Memory Output Exception (without StackTrace) in the log.
Most likely it never reaches the XSLT processor and get killed during parsing.

fixed in lo8, though the excel-ml transformation is extreamly slow for the
attached example, it will now complete after some minutes without running out of
memory.

please verify

re-open issue and reassign to fst@openoffice.org

reassign to fst@openoffice.org

reset resolution to FIXED

reassign to fst@openoffice.org

reset resolution to FIXED

There is still a problem with the SpreadsheetML transformation, which cuases it
to hang or stackoverflow with the attached file. The heap memory problem however
is solved, as can ve verified with the identity transformation (flat.xsl).

There is a new issue (i56322) for the recursion problem in the SpreadsheetML
transformation.

For clarification, the new recursion problem issue is i56326 not i56322 as
stated earlier.

found fixed on cws lo8 using Linux and Windows build

The problem (Java Heap exception) still occurs with a larger document (e.g.
21000 rows and 256 columns, which is still 2/3 of the capacity).
As all XSLT filter are limited by this, the issue is reopened.

Try again, Lars

Adjusted target milestone to OOo 2.0.2 as all XSLT filter suffer from this issue
(even two default filter). Even it happen with huge document only, therefore no P2.
Going to write TZ for OOo 2.0.2 confirmation.

and now it's yours :)

Won't be able to fix this for OOo 2.0.2, retarget to OOo 2.0.3

postponed to OOo 3.0

Not able to fix it in OOo 3.0 to overload, change target to OOo 3.x!
Is anybody able to provide me with a patch for this problem?
Thanks in advance,
Svante