<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - LO steadily increases memory usage until system freezes (lots of files open)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=131651#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - LO steadily increases memory usage until system freezes (lots of files open)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=131651">bug 131651</a> from <a class="email" href="mailto:bjorn.wastvedt@gmail.com" title="Bjorn Wastvedt <bjorn.wastvedt@gmail.com>"> Bjorn Wastvedt</a> <pre>(In reply to Timur from <a href="show_bug.cgi?id=131651#c7">comment #7</a>) > Content can be obfuscated by replacing each char with X. > But, we can only analyze source .ODT when saving to .DOC or .DOCX and > experiencing issues. > If first save was to .DOC, no help.. > If MS .DOC was saved to .ODT in LO, I guess that qualifies for acceptable > report. > Footnotes may be suspicious, as in <a class="bz_bug_link bz_status_NEW " title="NEW - FILEOPEN: slow loading and dump of .docx with lots of footnotes (see Comment 27 and Comment 43)" href="show_bug.cgi?id=76260">bug 76260</a>. > > Note: if responding to the whole previous post, no need to quote. Hi, Indeed: an MS .DOC was saved to .ODT in LO. Today, I found a workaround, by selecting all and copying into a new file. I think this avoids the problem. Should I close the bug, or should we pursue it (for the good of LO)?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>