<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - VIEWING: When the document displays !broken!! instead of the correct text, writer can lock up" href="https://bugs.documentfoundation.org/show_bug.cgi?id=121618#c15">Comment # 15</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - VIEWING: When the document displays !broken!! instead of the correct text, writer can lock up" href="https://bugs.documentfoundation.org/show_bug.cgi?id=121618">bug 121618</a> from <a class="email" href="mailto:okdf@johnfreed.com" title="okdf@johnfreed.com <okdf@johnfreed.com>"> okdf@johnfreed.com</a> <pre>Some thoughts ... 1) The patch for <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - !!br0ken!! mysteriously appears in Spellcheck after some steps" href="show_bug.cgi?id=116725">bug 116725</a> (which also appears to have fixed <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - !!br0ken!! mysteriously appears in Spellcheck after some steps" href="show_bug.cgi?id=117155">bug 117155</a>) isn't really for spellcheck per se, but rather fixes a problem when doing a right-to-left selection of justified text. Since your text is justified, and you didn't report the direction of selection you made, it's possible that this patch fixed the problem. See <a href="https://gerrit.libreoffice.org/#/c/52979/">https://gerrit.libreoffice.org/#/c/52979/</a> 2) In addition to the errors you noted in <a href="http://bugs.documentfoundation.org/attachment.cgi?id=146935" name="attach_146935" title="The render errors, now highlighted and numbered">attachment 146935</a> <a href="http://bugs.documentfoundation.org/attachment.cgi?id=146935&action=edit" title="The render errors, now highlighted and numbered">[details]</a>, there was another in the original post that was not in the subsequent post. Specifically, the word "shrug" is lost in the original attachment. So it appears that the error began earlier. Also, it seems that the first exclamation point in !!br0ken!! has vanished. I suspect it's related to the notion that an extra word was added but the paragraph was not rejustified. I can see how that would mess up a renderer; I would not expect pile-on effects to crash the entire program, however. 3) I downloaded the obfuscated document and determined (by searching for "wix, ix xox") that the problem was on page 233. I tried doing some right-to-left highlighting and changing; no problems. Using version 6.2.6.2, build 6.2.6.2-1.fc30 on Fedora. 4) I suppose the bigger problem is not the arrival of "br0ken" but rather that Writer can crash when the text that led to "br0ken" is displayed. It appears that "br0ken" appears only once in the live codebase (see <a href="https://opengrok.libreoffice.org">https://opengrok.libreoffice.org</a>) so at least that's one fewer thing to worry about. 5) The display part of the bug can probably be closed and marked as fixed per my first paragraph above. It can always be reopened. 6) To test the underlying problem (the crashing of the program), a programmer could force a call to that section of the code (/core/sal/rtl/strtmpl.cxx, line 1379) and see what happens. Above my pay grade.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>