Bug 126158 - Table layout loop under extreme conditions
Summary: Table layout loop under extreme conditions
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.4.7.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace, perf
Depends on:
Blocks: Writer-Tables Writer-Table-Layouting
  Show dependency treegraph
 
Reported: 2019-06-29 12:01 UTC by Telesto
Modified: 2025-10-29 03:12 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Screencast (7.35 MB, video/mp4)
2019-06-29 12:02 UTC, Telesto
Details
Example file (23.00 KB, application/vnd.oasis.opendocument.text)
2019-06-29 12:51 UTC, Telesto
Details
Example file (19.59 KB, application/vnd.oasis.opendocument.text)
2019-07-08 20:42 UTC, Telesto
Details
Perf flamegraph (36.07 KB, image/svg+xml)
2021-09-10 18:28 UTC, Buovjaga
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2019-06-29 12:01:39 UTC
Description:
Table layout loop under extreme conditions

Steps to Reproduce:
1. Open attachment 147138 [details]
2. CTRL+A + CTRL+C
3. CTRL+N
4. CTRL+V
5. Paste inside the last cell at the right
6. Paste inside the last cell (at the right
7. Click the large empty space -> Layout loop starts 



Actual Results:
Loop

Expected Results:
No loop?


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.4.0.0.alpha0+ (x86)
Build ID: c2cb467a1e5194c56bb65706b7965fb2c9241b8f
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-06-29_00:11:35
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: threaded
Comment 1 Telesto 2019-06-29 12:02:43 UTC
Created attachment 152465 [details]
Screencast
Comment 2 Telesto 2019-06-29 12:51:10 UTC
Created attachment 152466 [details]
Example file

Probably the same thing.. but bit easier the reproduce
1. open the attached file
2. CTRL+A & CTRL+C
3. CTRL+V -> Document is responsive but 100% (aka 25%) never-ending [stopped after 3 minutes or so] CPU utilisation in the background
Comment 3 Telesto 2019-07-08 20:42:49 UTC
Created attachment 152654 [details]
Example file

More basic example
1. Open the attached file
2. CTRL+A & CTRL+C
3. CTRL+N
4. CTRL+V
5. CTRL+V
6. CTRL+Z (2x)
7. CTRL+V -> Wait
Comment 4 Dieter 2019-07-11 17:28:37 UTC
(In reply to Telesto from comment #3)
> Created attachment 152654 [details]
> Example file
> 
> More basic example
> 1. Open the attached file
> 2. CTRL+A & CTRL+C
> 3. CTRL+N
> 4. CTRL+V
> 5. CTRL+V
> 6. CTRL+Z (2x)
> 7. CTRL+V -> Wait

I confirm it with

Version: 6.4.0.0.alpha0+ (x64)
Build ID: ae823e4633a76d13cebc6432b9e44b9b2862326b
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2019-06-26_23:06:07
Locale: de-DE (de_DE); UI-Language: en-US
Calc: threaded

Writer becomes unresponsive.
Comment 5 Telesto 2019-07-11 20:07:03 UTC
Also in
4.4.7.2
Comment 6 Buovjaga 2021-09-10 18:28:56 UTC
Created attachment 174954 [details]
Perf flamegraph

(In reply to Telesto from comment #3)
> Created attachment 152654 [details]
> Example file
> 
> More basic example
> 1. Open the attached file
> 2. CTRL+A & CTRL+C
> 3. CTRL+N
> 4. CTRL+V
> 5. CTRL+V
> 6. CTRL+Z (2x)
> 7. CTRL+V -> Wait

Waited for some seconds taking the trace, started tracing only before step 7.

Version: 7.3.0.0.alpha0+ / LibreOffice Community
Build ID: e6a8d312d3d7e5d81c56d5ccc0508116dd283f1f
CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Comment 7 QA Administrators 2023-09-11 03:13:42 UTC Comment hidden (obsolete)
Comment 8 Dieter 2023-10-29 14:37:32 UTC
Still the same with

Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 7fff4e2ca6739928f72e5f0d2eb5820823916769
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL threaded
Comment 9 QA Administrators 2025-10-29 03:12:41 UTC
Dear Telesto,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug