<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Crash in: CompareSwOutlineNodes::operator()(SwNode * const &,SwNode * const &)"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=134780#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Crash in: CompareSwOutlineNodes::operator()(SwNode * const &,SwNode * const &)"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=134780">bug 134780</a>
from <span class="vcard"><a class="email" href="mailto:lo_bugs@iseries-guru.com" title="Terrence Enger <lo_bugs@iseries-guru.com>"> <span class="fn">Terrence Enger</span></a>
</span></b>
<pre>I am giving up my attempt to bibisect this bug.
Working on debian-buster in bibisect-linux-64-6.0, after I bibisected
down to an entirely implausible commit, I have determined:
(*) One commit can give both crash and no-crash results.
(*) Slowing down execution of undo and redo (my test had 5 times
"<ctrl>+Z" then 5 times "<ctrl>+Y") seems to increase the
likelihood of a crash.
(*) In version oldest, I reached an apparent successful end of the
test (no crash yet; LO responded to <left> <left>) and then typed
"<ctrl>+X k" (old habit from emacs). *Now* LO crashed with
SIGABRT from a STL function called from frame #14 in
SwOutlineNodes::Seek_Entry; this is like the other disable-debug
crashes I have looked into.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>