https://bugs.documentfoundation.org/show_bug.cgi?id=95225
--- Comment #8 from John <j...@tesco.net> --- (In reply to Eike Rathke from comment #4) > As already noticed, the document is not empty. It contains two text area > form controls in exactly the same place and both have their visibility set > to invisible, hence the document *appears* to be empty. One of the forms > contains a long string (7724 characters) as text area value, which is a > Base64 encoded binary. I didn't investigate further, but it might be some > graphics related file and contains (apparently the title) "Profit & Loss" > and some notions of Arial font. > > The time spent might be due to the long string which is tried to wrap into a > text area but since there are no words it can't be wrapped and the iterator > just eats along on the string. > > If someone wants to run it with callgrind and find the actual bottleneck of > this abuse.. until then regard it as hit shappens. Eike, of course you're right in saying > It contains two text area form controls I can see this in the content.xml Ypu wrote: > in exactly the same place and both have their visibility set > to invisible, hence the document *appears* to be empty. I didn't notice that. You wrote: > I didn't investigate further, but it might be some > graphics related file and contains (apparently the title) "Profit & Loss" > and some notions of Arial font. That all makes sense, since Quickbooks was exporting a Profit & Loss report. I've had a quick look at the original .xlsx file saved from Excel. It has a section <controls> <control shapeId="1025" r:id="rId3" name="FILTER"/> <control shapeId="1026" r:id="rId4" name="HEADER"/> </controls> which I suppose generated the offending section in the .ods file beginning <form:textarea form:name="FILTER" form:control-implementation="ooo:com.sun.star. form.component.TextField" xml:id="control1" form:id="control1" form:current-valu e="AQCgFlByb2ZpdCAmIExvc3MAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA When I have access to a MS Windows machine, I'll cut down the file in MS Excel and save as xlsx. One could argue that the original bug is in reading the xlsx file. John -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
