[upstream] Writer hangs for over 20 minutes loading a 3MB, 450-page DOCX
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
LibreOffice |
Fix Released
|
Medium
|
|||
libreoffice (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Trying to load the attached DOCX results in a hang. I force-quit after 20 minutes. The DOCX was created in MS Word (2013 I think), and is about 450 pages, thousands of footnotes, but no graphics AFAIK.
I am using the latest package provided by snap. LibreOffice 6.1.2.1. Ubuntu 18.04.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice-writer (not installed)
ProcVersionSign
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 4 23:50:54 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-06-03 (488 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: Upgraded to bionic on 2018-06-06 (119 days ago)
Changed in df-libreoffice: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
summary: |
- Writer hangs for over 20 minutes loading a 3MB, 450-page DOCX + [upstream] Writer hangs for over 20 minutes loading a 3MB, 450-page DOCX |
Changed in df-libreoffice: | |
status: | Confirmed → In Progress |
Changed in df-libreoffice: | |
status: | In Progress → Fix Released |
I can observe the issue in an up-to-date bionic amd64 VM. Opening the attached document and rendering it completely took 32 minutes. This is an insane amount of time to load a 516 pages document (153316 words, 927209 characters), but it eventually completed and once done the document can be navigated and edited just fine, as far as I can tell.
If there isn't one already, can you please report a bug upstream at https:/ /bugs.documentf oundation. org/enter_ bug.cgi? product= LibreOffice& format= guided, and share the link to that bug here? Thanks!