Bug 84698 - crash when replacement is triggered by new paragraph
Summary: crash when replacement is triggered by new paragraph
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) Master
Hardware: Other All
: medium normal
Assignee: Caolán McNamara
Whiteboard: BSA target:4.4.0
Keywords: regression
Depends on:
Reported: 2014-10-05 21:33 UTC by Regina Henschel
Modified: 2014-10-06 13:49 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

picture of Assertion message (19.96 KB, image/png)
2014-10-05 21:33 UTC, Regina Henschel

Note You need to log in before you can comment on or make changes to this bug.
Description Regina Henschel 2014-10-05 21:33:40 UTC
Created attachment 107381 [details]
picture of Assertion message

Start with a new Writer document.
Make sure the AutoCorrect option "Use replacement table" is enabled.
Make sure the replacement table contains the item i --> I
Write an i and then press Enter key. --> Crash.

The crash is triggered with any replacement followed by an action with results in a new line. For example the crash is triggered too, when you write the i in a table cell and then press the tabulator key to move to next cell.
Comment 1 Regina Henschel 2014-10-05 21:36:58 UTC
I see the error in
Build ID: 86a3fe47a66950e26d23d7d7f2680fa7d4fb0839
TinderBox: Win-x86@39, Branch:master, Time: 2014-10-05_02:45:20

The version Version:
Build ID: 6ff819b65674ae6c83f3cbab9e4a4c2b292a7a94
does not have this error.
Comment 2 Terrence Enger 2014-10-06 03:05:14 UTC
Working in the daily dbgutil bibisect repository, I see from `git bisect good`:

    commit 8c0ffaa3f2ace1b3a8e8e1db44b11ba083637e4d
    Author: Miklos Vajna <vmiklos@collabora.co.uk>
    Date:   Mon Sep 1 09:48:23 2014 +0000


    :100644 100644 de56afe3d5f5e122723947b24311bd00acad1f70 60248ccd1189423ee8b6cafc100cfe547e335431 M	build-info.txt
    :040000 040000 f22263c2481b8cdc146b58a23b60c9ec2d6f56f0 7e57ec88799dc9cff16206c4351dec8337982f7a M	opt

and from `git bisect log`:

    # bad: [3bd90766c05c07c4a39e36cb1d3106b0016983d4] 2014-10-05
    # good: [b3130c846de5cf1b4be48b48dfc780bb369549fa] 2014-05-21
    git bisect start 'origin/master' 'oldest'
    # good: [5ed7df78a02df9f716188ab12cc6f641f479b6d1] 2014-07-29
    git bisect good 5ed7df78a02df9f716188ab12cc6f641f479b6d1
    # bad: [8c0ffaa3f2ace1b3a8e8e1db44b11ba083637e4d] 2014-09-01
    git bisect bad 8c0ffaa3f2ace1b3a8e8e1db44b11ba083637e4d
    # good: [43ab1b68274782b4dcfc69a5662179dcf00e9eab] 2014-08-15
    git bisect good 43ab1b68274782b4dcfc69a5662179dcf00e9eab
    # good: [4e2fde03fde233ff2e0d0b965a6fc5f5bb1370e7] 2014-08-23
    git bisect good 4e2fde03fde233ff2e0d0b965a6fc5f5bb1370e7
    # good: [2c5389138b550e7af1952c1770f6513757f72fbd] 2014-08-27
    git bisect good 2c5389138b550e7af1952c1770f6513757f72fbd
    # good: [a8232b4c392ff3508dc1a7b6ab5dd9a6d2bfdd99] 2014-08-29
    git bisect good a8232b4c392ff3508dc1a7b6ab5dd9a6d2bfdd99
    # good: [db4bc4671fbec1a556703a0fb0046aed7bb45d90] 2014-08-31
    git bisect good db4bc4671fbec1a556703a0fb0046aed7bb45d90
    # first bad commit: [8c0ffaa3f2ace1b3a8e8e1db44b11ba083637e4d] 2014-09-01