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

            Bug ID: 146976
           Summary: Writer Crashes After Opening A Large File
           Product: LibreOffice
           Version: 7.2.5.2 release
          Hardware: All
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: libreoffice-bugs@lists.freedesktop.org
          Reporter: mxr...@gmail.com

Description:
Writer has many, many problems with large (>1.75Mb) files, including crashing.

Steps to Reproduce:
1. Open file.
2. Navigate to near the end of the document & save it.
3. Open the file again so the file is opened near the end of the file.
4. Window > New Window.
5. In the new window, click on the vertical slider bar. (If it doesn't crash,
repeat, pressing Ctrl-Home first).

Actual Results:
crashes

Expected Results:
To go to the top of the document.


Reproducible: Always


User Profile Reset: No



Additional Info:
All versions of Windows 10, on 32- & 64-bit installations.
File size 2000 pages & larger, 2Mb or larger. No images. Just text.
-----------------
Confirmed Writer versions: 7.1 thru latest release of 7.2
-----------------
This is an inherited problem from Open Office. It's a design problem in that
shortly after a file is opened the software does something (scans the entire
document?). It is not apparent on small files because it happens so quickly. A
large file makes it extremely apparent. 

There are many other problems this creates. Even when it doesn't crash, the
number of pages in the file is oftentimes incorrect until the 'scanning' stops.
When halfway down in the document or lower, the pages keep jumping around,
preventing moving to the desired location. It also crashes in other scenarios,
but here's the easiest procedure I've found to reproduce the crash. I could go
on, but you get the point. Until well after the 'scanning' is complete, the
file isn't usable.

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

Reply via email to