Bug Hunting Session
Bug 88126 - FILEOPEN Writer hangs on opening a docx that MSO says corrupt but Open XML Productivity Tools finds no validation errors
Summary: FILEOPEN Writer hangs on opening a docx that MSO says corrupt but Open XML Pr...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:docx, haveBacktrace, perf
Depends on:
Blocks: DOCX-Opening
  Show dependency treegraph
 
Reported: 2015-01-06 19:43 UTC by Jos van den Oever
Modified: 2019-02-15 15:10 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments
file that hangs libreoffice when opened (39.69 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2015-01-06 19:43 UTC, Jos van den Oever
Details
xslt used for greeking the original file (616 bytes, text/xml)
2015-01-06 19:43 UTC, Jos van den Oever
Details
debug WinDBG from procdump (12.16 KB, text/text)
2017-07-19 12:21 UTC, Timur
Details
Word 2016 repaired bugdoc (39.02 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2019-02-06 15:31 UTC, Luke
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jos van den Oever 2015-01-06 19:43:17 UTC
Created attachment 111867 [details]
file that hangs libreoffice when opened

The attached file causes LibreOffice Writer to hang when it is opened. The CPU is stuck at 100% and memory use keeps increasing.

The problem is reproducible.

The file is a greeked version of the original. The file was greeked by unzipping and running the attached xslt over the contents of the xml files. This replaced all [a-zA-Z0-9] with 'a'. This changed file also hangs LibreOffice.
Comment 1 Jos van den Oever 2015-01-06 19:43:48 UTC
Created attachment 111868 [details]
xslt used for greeking the original file
Comment 2 Jos van den Oever 2015-01-06 19:44:06 UTC
Version: 4.3.3.2
Build ID: 430m0(Build:2)
Comment 3 Robinson Tryon (qubit) 2015-01-07 00:42:45 UTC Comment hidden (obsolete)
Comment 4 Robinson Tryon (qubit) 2015-01-07 00:51:50 UTC
TESTING with Ubuntu 14.04 (x86-64) + 
LO Version: 4.5.0.0.alpha0+
  Build ID: 5c60dab390d66a4d5abeaf548efecf3913b90839
  TinderBox: Linux-rpm_deb-x86_64@46-TDF
  Branch:master
  Time: 2014-12-31_00:20:30
  Locale: en_US

(In reply to Jos van den Oever from comment #0)
> Created attachment 111867 [details]
> file that hangs libreoffice when opened
> 
> The attached file causes LibreOffice Writer to hang when it is opened. The
> CPU is stuck at 100% and memory use keeps increasing.

CONFIRMED -- 100% CPU and memory creeping upwards
I only let it go for about 45 seconds.

Status -> NEW

It's possible that this is a performance issue, but I'm not sure. I'll test on a beefier machine (this machine is a Core2duo T8300 @2.4GHz + 4G RAM)
Comment 5 Robinson Tryon (qubit) 2015-01-07 01:01:49 UTC
(In reply to Robinson Tryon (qubit) from comment #4)
> [test with] attachment 111867 [details]
> > file that hangs libreoffice when opened
> > 
> > The attached file causes LibreOffice Writer to hang when it is opened. The
> > CPU is stuck at 100% and memory use keeps increasing.
> ..
> It's possible that this is a performance issue, but I'm not sure. I'll test
> on a beefier machine (this machine is a Core2duo T8300 @2.4GHz + 4G RAM)

Hangs on a Mac Mini as well (quad-core i7 + 16G RAM).

Platform -> All
Whiteboard -> perf
Comment 6 Jos van den Oever 2015-08-23 21:07:01 UTC
This is still a problem in LibreOffice 5.0.0.5.
Opening bug.docx hangs one cpu core at 100% for at least a minute.
Comment 7 Robinson Tryon (qubit) 2015-12-09 18:07:57 UTC Comment hidden (obsolete)
Comment 8 Timur 2017-07-19 12:21:54 UTC
Created attachment 134734 [details]
debug WinDBG from procdump
Comment 9 Timur 2017-07-19 13:23:23 UTC
When someone submits a bug, always need to be asked how document was created. Hpw was original created (MSO or LO) and how attached docx was created.
If this DOCX was saved or changed by LO then it's another FILESAVE bug, that can be fixed only if reproducible with steps. 
Othwerwise, this FILEOPEN bug is useless and can be closed as INVALID. 
This DOCX cannot be open with MSO, says the file is corrupt. 
What's not clear is how Open XML Productivity Tools finds no validation errors.
So I set back to Needinfo.
Comment 10 Jos van den Oever 2017-07-19 19:44:50 UTC
I do not the original file anymore. The file was created with MS Office. It was greeked to hide confidential information.
Comment 11 Timur 2017-07-20 11:55:29 UTC
I guess we may change this bug from ability to open file to message that file is corrupt and cannot be open, maybe repaired. Hang is not acceptable.
Comment 12 QA Administrators 2018-07-21 02:40:23 UTC Comment hidden (obsolete)
Comment 13 Timur 2018-07-23 10:23:25 UTC
Repro 6.2+.
Comment 14 Luke 2019-02-06 15:31:05 UTC
Created attachment 148955 [details]
Word 2016 repaired bugdoc