Bug 148241 - LO Writer has issues editing index entries in tables
Summary: LO Writer has issues editing index entries in tables
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.2.6.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks: Concordance-File
  Show dependency treegraph
 
Reported: 2022-03-28 21:53 UTC by Erick
Modified: 2023-05-03 07:04 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Image showing field highlight outside table for entry (80.09 KB, image/png)
2022-03-28 21:53 UTC, Erick
Details
LO Writer TestDocument (20.92 KB, application/vnd.oasis.opendocument.text)
2022-04-05 11:50 UTC, Erick
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Erick 2022-03-28 21:53:44 UTC
Created attachment 179175 [details]
Image showing field highlight outside table for entry

Problem: I have created a subdocument using writer that contains tables and have indexed certain names while inside those tables. The problem occurs when I attempt to edit those indexed entries. The editor becomes confused and highlights fields outside the table. I would have assumed that if I could index entries inside a table, then it is supported and by extension I would be able to edit them. After editing a few entries the application may become so confused that it will hang and eventually crash.

My current workaround is to only focus on the editor and when the appropriate entry comes up, ignore the hightlight and delete or change the entry using the edit window only. I have to get out of edit mode every one or two entries and save, due to the potential for the application to crash.

I have a small example odt file for recreate.

Version: 7.2.6.2 (x64) / LibreOffice Community
Build ID: b0ec3a565991f7569a5a7f5d24fed7f52653d754
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded
Comment 1 Ezinne 2022-04-04 21:47:42 UTC
Please can you attach a sample file to aid in testing the bug?
Comment 2 Erick 2022-04-05 11:50:24 UTC
Created attachment 179324 [details]
LO Writer TestDocument

I have attached a simple testcase showing the bug, it is easy to re-create.

BTW, there are other regressions in 7.2 having to do with master documents, etc., which have forced me back to 6.5.  So, am very suspicious about the testing on the latest release.
Comment 3 QA Administrators 2022-04-06 03:46:15 UTC Comment hidden (obsolete)
Comment 4 raal 2022-05-27 22:11:35 UTC
Tested with Version: 7.4.0.0.alpha1+ / LibreOffice Community
Build ID: b6e0ae1b1bad5e222e21bbb4b2a158c1fc6f9779
CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: x11
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded Jumbo
I can reproduce freeze/crash: Add cursor to the field before the table, for example "Avellino". Edit-Reference-Index entry, the dialog opens. Click on the Next entry button, LO freeze.

Doesn't crash in Version: 5.4.0.0.alpha1+, marking as regression.

About selecting - when I add cursor on the field inside the table, then whole table is selected after few clicks on the Next entry.
Comment 5 raal 2023-04-25 16:54:18 UTC
(In reply to raal from comment #4)
> Tested with Version: 7.4.0.0.alpha1+ / LibreOffice Community
> Build ID: b6e0ae1b1bad5e222e21bbb4b2a158c1fc6f9779
> CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: x11
> Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
> Calc: threaded Jumbo
> I can reproduce freeze/crash: Add cursor to the field before the table, for
> example "Avellino". Edit-Reference-Index entry, the dialog opens. Click on
> the Next entry button, LO freeze.
> 

Clicking Next entry few times freeze LO, 100% of CPU used.
This seems to have begun at the below commit in bibisect repository/OS bibisect-linux-64-6.2.
Adding Cc: to Caolán McNamara ; Could you possibly take a look at this one?
Thanks
 3aab96b35d868d30192be278ac4f39e68b2b7f85 is the first bad commit
commit 3aab96b35d868d30192be278ac4f39e68b2b7f85
Author: Jenkins Build User <tdf@pollux.tdf>
Date:   Mon Nov 5 15:21:20 2018 +0100

    source e3c6c89588fc6b85663444d701f782e73bb572c1

62775: weld SwIndexMarkModalDlg cluster | https://gerrit.libreoffice.org/c/core/+/62775