Description: After loading this document... Jumping to last page, then going to next-to-last page takes LO >1 hour vs. Microsoft Word's <30 seconds. Steps to Reproduce: 0) Open attachment 191261 [details]. - It'll take a while... it's ~2 million words + ~1450 DOCX pages. After file finishes opening: 1) Press CTRL+END - To jump to final page. 2) Press PAGE UP. - To jump up one page. - - - - - - - - - This is how long it takes: Microsoft Word 2016: 1) 28 secs 2) instant LibreOffice 7.6.3: 1) 7 mins 42 secs 2) >37 mins - (I gave up after 37 mins.) Actual Results: >1 hour of waiting. Expected Results: <2 minutes of waiting. Reproducible: Always User Profile Reset: No Additional Info: Tested on: Version: 7.6.3.2 (X86_64) / LibreOffice Community Build ID: 29d686fea9f6705b262d369fede658f824154cc0 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded and: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 25276df12abd9d002f7f899900434617b256f745 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded - - - - - - - - - For a little more info, also see: - Bug #158556 (Comment 2 and beyond) - Issue focuses on very slow open. - Mike Kaganski recommended I open a separate bug for this performance-after-load issue.
Unbearably slow to open with: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 2cedb1a19ad605df4e148589e9027512e4dd9265 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded So haven't been able to reproduce.
(In reply to Stéphane Guillou (stragu) from comment #1) > Unbearably slow to open with: > > Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community > [...] Yes. To initially open the DOCX will currently take: - ~10.5 minutes on LO 7.6.4 - ~7.5 minutes on LO 24.8.0 (See Bug #158556 for status on that LOADING speed.) This report was split to focus on atrocious performance AFTER LOAD instead. - - - So if you're going to test this DOCX... definitely get up and stretch, make yourself a cup of tea, and return to the computer after. :P (Personally, I sat there watching a video on my phone + timer running while keeping the corner of my eye for changes to my screen.)
(In reply to Tex2002ans from comment #0) > Description: > After loading this document... Jumping to last page, then going to > next-to-last page takes LO >1 hour vs. Microsoft Word's <30 seconds. > > Steps to Reproduce: > 0) Open attachment 191261 [details]. > - It'll take a while... it's ~2 million words + ~1450 DOCX pages. > > After file finishes opening: > > 1) Press CTRL+END > - To jump to final page. After this, it took maybe 30 minutes to stabilise for me. > 2) Press PAGE UP. > - To jump up one page. This action is instant for me. Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 125fc2ce861c82592b261f2992c893b414396e56 CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded
As the summary talks about Ctrl+End, let's set to NEW.
(In reply to Buovjaga from comment #3) > > After file finishes opening: > > > > 1) Press CTRL+END > > - To jump to final page. > > After this, it took maybe 30 minutes to stabilise for me. > > > 2) Press PAGE UP. > > - To jump up one page. > > This action is instant for me. Thanks for testing, Buovjaga. So you: 1. CTRL+END - Waited 30 mins for LO to stabilize. 2. Then tried the PAGE UP? Where I was mostly doing: 1. CTRL+END - When LO finally made it to the final page... 2. I instantly pressed PAGE UP. So while you were waiting there for 30 minutes, stabilizing after Step 1, that's probably when my LO was "taking >30 minutes on my end to PAGE UP"! - - - I retested this document on the latest: - Word 365 (2401, Build 17231.20194) - + Windows 11 It was a tiny bit faster than my comment 0: 1) 25 seconds - Down from 28 seconds in Word 2016. 2) Instant
Yeah, I was doing it in the live stream, working on other bugs and checking the situation from time to time. After it didn't go (Not responding) anymore and the pagination had settled, I hit page up and didn't have to wait.