<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Writer FILEOPEN, FORMATTING, VIEWING: very slow, hanging when opening files with complex tables" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125171#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Writer FILEOPEN, FORMATTING, VIEWING: very slow, hanging when opening files with complex tables" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125171">bug 125171</a> from <a class="email" href="mailto:darktemplar@basealt.ru" title="Aleksei Nikiforov <darktemplar@basealt.ru>"> Aleksei Nikiforov</a> <pre>Created <a href="http://bugs.documentfoundation.org/attachment.cgi?id=158650" name="attach_158650" title="slow-large-v2.odt">attachment 158650</a> <a href="http://bugs.documentfoundation.org/attachment.cgi?id=158650&action=edit" title="slow-large-v2.odt">[details]</a> slow-large-v2.odt (In reply to Julien Nabet from <a href="show_bug.cgi?id=125171#c12">comment #12</a>) > You can retest the bug with LO 6.4.1 but no info since there was no comment. I've built from sources and tried following version: Version: 6.4.2.1 Build ID: c92dba0b4728c0ec26c4b83e2c0fbf3284425375 CPU threads: 12; OS: Linux 5.5; UI render: default; VCL: kf5; Locale: en-US (C); UI-Language: en-US Calc: threaded LO opens example files pretty fast, even larger ones. But on large examle even while it doesn't hangs for long time after opening file anymore, it still hangs for a bit and LO works pretty slow, constantly consuming 100% CPU according to 'top'. I've tried replacing every word 'text' with phrase 'longer string with some spaces' to see if it'd make LO work slower. Not sure about result, I guess it might work a bit slower. I'm attaching resulting file. (In reply to Mike Kaganski from <a href="show_bug.cgi?id=125171#c13">comment #13</a>) > An idea would be to add a flag to the follow row frame indicating that it > should not look back for the total row height before when the current height > is greater than minimal ... or even not the flag, but simply the "previous > height" to avoid looking back at all? Caching results of size and position calculations might help. But in that case events affecting either size of position should invalidate such caches at least partially.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>