Description: A page layout loop hitting icu_67::RuleBasedBreakIterator::handleNext over and over Steps to Reproduce: 1. Open attachment 162249 [details] 2. CTRL+A 3. CTRL+C 4. CTRL+V 5. Go to multi page view -> correct the images overlapping the footnotes as far as possible 6. Go to top of the page 7. Press CTRL+Enter 8. Insert -> Table of content -> Table of content & press OK 9. CTRL+Z 10. CTRL+Y -> two possible out comes.. some iterating an finalizes .. or gets stuck in a loop Like because some anchor is moving up down of a footnote having issues to find a proper place icu_67::RuleBasedBreakIterator::handleNext ubrk_swap_67 ubrk_swap_67 ubrk_swap_67 icu_67::RuleBasedBreakIterator::preceding com_sun_star_i18n_BreakIterator_get_implementation i18nsearch_component_getFactory SwTextFrame::SwitchRTLtoLTR SwPageDesc::SetRegHeight SwDrawTextInfo::SetPosMatchesBounds SwDrawTextInfo::SetPosMatchesBounds SwTextFrame::FormatLine SwTextFrame::Format_ SwTextFrame::Format_ SwTextFrame::Format SwViewOption::IsWhitespaceHidden SwFrame::OptPrepareMake SwViewShell::EnableSmooth SwViewShell::EnableSmooth SwTextFrame::HasRepaint SwLayoutFrame::MoveLowerFootnotes SwViewShell::LayoutIdle SwBreakIt::GetForbidden Scheduler::ProcessTaskScheduling create_SalInstance [00007FFFCD508386] [00007FFFCD507EB1] Application::Execute SfxTabPage::set_visible ImplSVMain soffice_main main main BaseThreadInitThunk RtlUserThreadStart Actual Results: Loop Expected Results: No loop Reproducible: Sometimes User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: 43c60ce1ac7629a1462e927e6ff937469f58f743 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
Created attachment 162258 [details] Example file Yet another way 1. Open the attached file 2. CTRL+A 3. CTRL+X 4. CTRL+V
Created attachment 162327 [details] Example file Does the same
Created attachment 162328 [details] Example file
Also in Version: 5.0.6.3 Build ID: 490fc03b25318460cfc54456516ea2519c11d1aa Locale: en-US (nl_NL) Based on attachment 162328 [details] Not in Versie: 4.4.7.2 Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600 Locale: nl_NL
@Xisco I assume a mistake.. easyHack
No looping with steps from description or comment 1 Arch Linux 64-bit Version: 7.1.0.0.alpha0+ Build ID: cb72269f93a20dd175dae3dcf30740c9931e7684 CPU threads: 8; OS: Linux 5.7; UI render: default; VCL: kf5 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 24 June 2020
(In reply to Buovjaga from comment #6) > No looping with steps from description or comment 1 > > Arch Linux 64-bit > Version: 7.1.0.0.alpha0+ > Build ID: cb72269f93a20dd175dae3dcf30740c9931e7684 > CPU threads: 8; OS: Linux 5.7; UI render: default; VCL: kf5 > Locale: fi-FI (fi_FI.UTF-8); UI: en-US > Calc: threaded > Built on 24 June 2020 Please try: comment 3 (gtk3)
(In reply to Telesto from comment #7) > (In reply to Buovjaga from comment #6) > > No looping with steps from description or comment 1 > > > > Arch Linux 64-bit > > Version: 7.1.0.0.alpha0+ > > Build ID: cb72269f93a20dd175dae3dcf30740c9931e7684 > > CPU threads: 8; OS: Linux 5.7; UI render: default; VCL: kf5 > > Locale: fi-FI (fi_FI.UTF-8); UI: en-US > > Calc: threaded > > Built on 24 June 2020 > > Please try: comment 3 (gtk3) no steps in comment 3. Please, clarify the steps to follow
(In reply to Xisco Faulí from comment #8) > (In reply to Telesto from comment #7) > > (In reply to Buovjaga from comment #6) > > > No looping with steps from description or comment 1 > > > > > > Arch Linux 64-bit > > > Version: 7.1.0.0.alpha0+ > > > Build ID: cb72269f93a20dd175dae3dcf30740c9931e7684 > > > CPU threads: 8; OS: Linux 5.7; UI render: default; VCL: kf5 > > > Locale: fi-FI (fi_FI.UTF-8); UI: en-US > > > Calc: threaded > > > Built on 24 June 2020 > > > > Please try: comment 3 (gtk3) > > no steps in comment 3. > Please, clarify the steps to follow Sorry, no steps needed.. only opening the file is enough :-). It's an idle loop process.. so file feels probably smooth.. except keeps processing in the background
(In reply to Telesto from comment #9) > Sorry, no steps needed.. only opening the file is enough :-). It's an idle > loop process.. so file feels probably smooth.. except keeps processing in > the background It is true that the CPU stays at 100% after opening attachment 162328 [details]. I guess I'll try bibisecting it.
(In reply to Buovjaga from comment #10) > (In reply to Telesto from comment #9) > > Sorry, no steps needed.. only opening the file is enough :-). It's an idle > > loop process.. so file feels probably smooth.. except keeps processing in > > the background > > It is true that the CPU stays at 100% after opening attachment 162328 [details] > [details]. I guess I'll try bibisecting it. For the record.. it's normal behavior, to some extend (maybe the first 30 seconds..)
(In reply to Telesto from comment #11) > (In reply to Buovjaga from comment #10) > > (In reply to Telesto from comment #9) > > > Sorry, no steps needed.. only opening the file is enough :-). It's an idle > > > loop process.. so file feels probably smooth.. except keeps processing in > > > the background > > > > It is true that the CPU stays at 100% after opening attachment 162328 [details] > > [details]. I guess I'll try bibisecting it. > > For the record.. it's normal behavior, to some extend (maybe the first 30 > seconds..) So what should we consider? 30 sec is good behaviour, infinite is bad? Or you see 30 sec always and think we should wait 30 sec and then do the steps from description? It seems to be infinite for me, not stopping even after minutes.
For me, the cpu usage goes down after ~20 seconds Version: 7.1.0.0.alpha0+ Build ID: e2b50a956cd34179d4f1e7f87834a94188011843 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
(In reply to Xisco Faulí from comment #13) > For me, the cpu usage goes down after ~20 seconds > > Version: 7.1.0.0.alpha0+ > Build ID: e2b50a956cd34179d4f1e7f87834a94188011843 > CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3 > Locale: en-US (en_US.UTF-8); UI: en-US > Calc: threaded Sounds a like a decent reference.. so 20 sec normal (longer is likely infinite so bad)
See also bug 134417 with some bibisects in the same area (maybe related)
A bibisected is probably not needed.. Betting on idle timer stuff. Likely even a duplicate
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