Writer goes hangs with high CPU and the only way to proceed is to kill it after the following steps.
Steps to Reproduce:
1. Copy all content from bug-content.odt:
- Open bug-content.odt, Ctrl+A, Ctrl+C.
2. Open bug-new-template.odt.
3. Open the Styles and Formatting side pane.
4. Paste it at the end of bug-new-template.odt:
- Ctrl+End, Ctrl+V.
Observe how the original A to D content is now 1 to 4 on both questions. This is probably a bug. However it is not the bug I am reporting.
5. Select the first set of possible answers, the ones that include 100, 200, 300 and 400 as options. Select them from the start of "100" to the end of "400".
6. Double click on style "Pregunta".
Writer goes hangs with high CPU and the only way to proceed is to kill it.
Writer should apply the style Pregunta.
User Profile Reset: No
Build ID: 1:5.2.1-1
CPU Threads: 8; OS Version: Linux 4.7; UI Render: default;
Locale: en-US (en_US.utf8); Calc: group
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.92 Safari/537.36
Created attachment 127936 [details]
File with the content to be copied
Created attachment 127937 [details]
Created attachment 127938 [details]
I'm reattaching bug-content.odt with a description that better matches the bug report.
@Meeks, @Maxim: Is a trace needed for this?
Build ID: 45a7137c6796f33fbf5b8f7cb64e293260d991cb
CPU Threads: 2; OS Version: Linux 3.19; UI Render: default;
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2016-10-13_23:38:06
Locale: en-US (en_US.UTF-8); Calc: group
@Buovjaga, @Aron: Any suggestions on how to move this forward?
Created attachment 132766 [details]
GDB trace of hang with 5.4 master
Arch Linux 64-bit, KDE Plasma 5
Build ID: f1f210866f9590eb59ef83b9ac0d434d7d29ef18
CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: kde4;
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on April 21st 2016
On pc Debian x86-64 with master sources updated yesterday, I could reproduce this.
I noticed this log repeatedly:
warn:legacy.osl:2401:1:sw/source/core/layout/flowfrm.cxx:2405: <SwFlowFrame::MoveBwd(..)> - layout loop control for layout action <Move Backward> applied!
** Please read this message in its entirety before responding **
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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Can't reproduce anymore on 184.108.40.206.
Thank you for your feedback.
Let's put this one to WFM then.
I too had the same problem. Is there any fix for it yet?