https://bugs.documentfoundation.org/show_bug.cgi?id=139843

Michael Stahl (allotropia) <michael.st...@allotropia.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|bibisectRequest             |bibisected, bisected,
                   |                            |haveBacktrace
             Blocks|                            |102593, 133092, 138327

--- Comment #9 from Michael Stahl (allotropia) <michael.st...@allotropia.de> ---
copying comments from bug 136409:


[tag] [reply] [−] Comment 6 Telesto 2020-09-03 20:04:10 CEST

Crash with
6.3

No crash on paste with
6.2

[tag] [reply] [−] Comment 7 Terrence Enger 2020-09-23 19:30:36 CEST

Created attachment 165798 [details]
bibisect-linux-64-6.3, tail of terminal output

Working in bibisect-linux-64-6.3 repository on debian-buster, I find
the bug started:

          commit    s-h       date
          --------  --------  -------------------
    good  717ce60f  43a7231c  2018-11-15 14:10:06
    bad   f7287b31  ae246b44  2018-11-15 14:10:06

for which the commit message is

    commit ae246b44da1708417aaaefe4f9186cfbbb9a9137
    Author:     Michael Stahl <michael.st...@cib.de>
    AuthorDate: Wed Nov 7 14:16:28 2018 +0100
    Commit:     Michael Stahl <michael.st...@cib.de>
    CommitDate: Thu Nov 15 15:10:06 2018 +0100

        sw_redlinehide_3: add second result to SwGetRefField

        ... and init it in SwGetRefField::UpdateField().

        Change-Id: I69af00678e84214d4a122d8b2d940fcdda5f4ccf


I waited for CPU usage to return to 0% before each operation.  This
introduces considerable delay, especially between first rendering of
the document and <Ctrl>+A.


When I probed the "good" versions, after LibreOffice correctly
responded to <Ctrl>+V, I continued with

5. CTRL+Q ALT+D

the <Alt>+D being a reponse to the question about saving the document
before quitting.)  In the probes of versions closest the first bad
version, LibreOffice promptly closed the Writer window and then
finished normally after about 3 more minutes with 100% CPU.  However,
two probes of the earliest versions in the repository, upon <Ctrl>+Q
<Alt>+D, crashed with a Signal 6.  A backtrace from this crash looks
quite different from the backtrace from a crash upon <Ctrl>+V.


I am removing keyword bibisectRequest and adding bibisected, bisected.

[tag] [reply] [−] Comment 8 Terrence Enger 2020-09-23 19:40:16 CEST

Created attachment 165799 [details]
backtrace from master

This backtrace is from a local build of commit b42d5557, 2020-09-10, built and
running on debian-buster, 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

I am removing keyword wantBacktrace and adding haveBacktrace.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=102593
[Bug 102593] [META] Paste bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=133092
[Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=138327
[Bug 138327] [META] sw_redlinehide regressions (track changes)
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to