Bug 134780 - Crash in: CompareSwOutlineNodes::operator()(SwNode * const &,SwNode * const &)
Summary: Crash in: CompareSwOutlineNodes::operator()(SwNode * const &,SwNode * const &)
Status: RESOLVED DUPLICATE of bug 119241
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.2.0.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisectRequest, haveBacktrace, regression
Depends on:
Blocks: Crash-Assert
  Show dependency treegraph
 
Reported: 2020-07-13 12:07 UTC by Telesto
Modified: 2020-07-26 21:45 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["CompareSwOutlineNodes::operator()(SwNode * const &,SwNode * const &)"]


Attachments
Example file (15.47 KB, application/vnd.oasis.opendocument.text)
2020-07-13 12:07 UTC, Telesto
Details
Screencast (2.90 MB, video/mp4)
2020-07-13 12:08 UTC, Telesto
Details
backtrace on Linux (11.76 KB, text/plain)
2020-07-20 14:41 UTC, Terrence Enger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-07-13 12:07:05 UTC
Created attachment 162966 [details]
Example file

This bug was filed from the crash reporting server and is br-ca82641f-3975-46fa-bb1c-f6b1368c7230.
=========================================

1. Open the attached file
2. Open a new file
3. Insert 2 sections -> insert section
4. Paste content from the attached file in both sections
5. Paste below the second
6. Undo everything
7. Redo everything

-> More those bugs reports already around so likely a dupe, but you never know
Comment 1 Telesto 2020-07-13 12:08:43 UTC
Created attachment 162967 [details]
Screencast
Comment 2 Telesto 2020-07-13 12:11:22 UTC
No crash with
Versie: 4.4.7.2 
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Locale: nl_NL
Comment 3 Telesto 2020-07-13 12:14:05 UTC
Also in 6.0

and in 5.2
Comment 4 Terrence Enger 2020-07-20 14:41:11 UTC
Created attachment 163328 [details]
backtrace on Linux

The crash happened on the fourth Redo.


This is from commit 0d45380c, configured

    --with-vendor=Terrence Enger
    --with-jdk-home=/usr/lib/jvm/default-java
    --enable-split-debug
    --enable-gdb-index
    --enable-ld=gold
    --enable-option-checking=fatal
    #--enable-dbgutil
    --enable-debug
    --without-system-postgresql
    --without-myspell-dicts
    --with-extra-buildid
    --without-doxygen
    --with-external-tar=/home/terry/lo_hacking/git/src
    --without-package-format

built and running on debain-buster.


I am setting keyword haveBacktrace and blocks Crash-Assert.
Comment 5 Terrence Enger 2020-07-20 16:58:06 UTC
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.
Comment 6 Terrence Enger 2020-07-20 17:09:34 UTC
Based on similarity of backtraces, I am marking this report
DUPLICATE of bug 134626.

*** This bug has been marked as a duplicate of bug 134626 ***
Comment 7 Telesto 2020-07-26 21:45:20 UTC

*** This bug has been marked as a duplicate of bug 119241 ***