https://bugs.documentfoundation.org/show_bug.cgi?id=158556

            Bug ID: 158556
           Summary: DOCX Document That Opens/Loads Extremely Slowly
           Product: LibreOffice
           Version: 7.6.3.2 release
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Description:
Attached document does all of these extremely slowly:

- Loading/Opening from scratch
- Jumping to last page
- PAGE UP from last page

Steps to Reproduce:
TEST #1: OPENING DOCUMENT

1) Double-Click on attached DOCX to open it.

Microsoft Word 2016:

- 43 secs

LibreOffice 7.6.3:

- 10 mins 20 secs

While:

- Microsoft Word initially opens it faster
- LibreOffice is staring at a white loading screen

After opening, they both still take quite a while to generate all the pages
too...

- - - - - - - - - - -

TEST #2: JUMP TO FINAL PAGE + PAGE UP

After document load:

1) Press Ctrl+End.
- (To jump to the end of the document.)

2) After reaching final page and document finishes loading:
- Press PAGE UP on keyboard.

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:
NOTE ON DOCUMENT: This was a DOCX document I generated by using ABBYY
Finereader 12 to:

- OCR a PDF.
- Export to DOCX.

It is a dictionary that is ~2 million words + ~1450 DOCX pages.

(Original was ~910 pages of dense, triple-column text.)

- - -

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to