Bug 40579 - FILEOPEN Crash opening docx file
Summary: FILEOPEN Crash opening docx file
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
3.4.3 release
Hardware: x86-64 (AMD64) macOS (All)
: medium critical
Assignee: Not Assigned
Keywords: regression
Depends on: 39384 39586 40588
  Show dependency treegraph
Reported: 2011-09-02 06:00 UTC by digital ant
Modified: 2011-12-23 13:25 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

example file edited and saved in word 2010 (33.43 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2011-09-02 06:30 UTC, digital ant
apple crash trace (42.36 KB, text/plain)
2011-09-02 07:29 UTC, Alex Thurgood

Note You need to log in before you can comment on or make changes to this bug.
Description digital ant 2011-09-02 06:00:43 UTC
LibreOffice 3.4.3 
OOO340m1 (Build:302)
On MacOSX 10.6.8 with Java 13.5

Received a resume and cover letter in two separate docx files. The Cover letter opened fine, but the resume crashed LibO 3.4.3 - just double clicking on the file caused the crash before the app opened. I have also tried opening it using the open button from the main LibO app window buy selecting the file and the file type (MS Word 2007/2010 XML) - same result.

We are using LibO 3.3.2 in our enterprise and the resume opened, it was blank, but it did not crash.

Below is the beginning of the crash output from OSX, if it helps. I am trying to get the sender to send me a modified version of the resume without personal information in it so I can upload it.

Process:         soffice [253]
Path:            /Applications/LibreOffice.app/Contents/MacOS/soffice
Identifier:      org.libreoffice.script
Version:         3.4.3 (???)
Code Type:       X86 (Native)
Parent Process:  launchd [114]

Date/Time:       2011-09-02 08:53:10.198 -0400
OS Version:      Mac OS X 10.6.8 (10K549)
Report Version:  6

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread:  0  Dispatch queue: com.apple.main-thread
Comment 1 digital ant 2011-09-02 06:30:19 UTC
Created attachment 50846 [details]
example file edited and saved in word 2010
Comment 2 digital ant 2011-09-02 06:31:01 UTC
changed version to 3.4.3 release
Comment 3 Alex Thurgood 2011-09-02 07:15:53 UTC
I can confirm that attempting to open this file also causes 3.3.4 and 3.4.2 to crash.

The file can be opened on OOo-dev 3.4.0, NeoOffice 3.2p5, NeoOffice 3.1.2.

It can also be opened successfully with the daily build from master :

LibO-dev 3.5.0 
Build ID: 44cc719-bca9bad-4eb4f62-260b7c1-0360e83

so there is obviously a fix in master which could be propagated to the 3.3.x/3.4.x branches.

Comment 4 Alex Thurgood 2011-09-02 07:29:02 UTC
Created attachment 50847 [details]
apple crash trace
Comment 5 Alex Thurgood 2011-09-02 07:35:14 UTC
Fixed in current master. Integration for 3.4?
Comment 6 Rainer Bielefeld Retired 2011-09-21 03:24:23 UTC
My current Master crashes with ANY WRITER document, so it's difficult to check whether the fix really works.

We have several additional "docx-crash" reports, I marked them as blockers for this one, we will have to check.

Additionally my "LibreOffice 3.4.3 RC2 - WIN7 Home Premium (64bit) German UI [OOO340m1 (Build:302)]" crashes when I try to open Attachment for "Bug 41013 - Incorrect pagination when document initially loaded".
Comment 7 Rainer Bielefeld Retired 2011-10-26 04:02:23 UTC
No problem with reporter's sample and with parallel installation of MinGW Master "LibO-dev 3.5.0 – WIN7 Home Premium (64bit) English UI [(Build ID:  2ba5d12-e8c71c5-41e7bcd-4b83b90)] (daily/MinGW_cross-compilation2011-10-25_00.12.09)"
(what ever that might mean)
Comment 8 Rainer Bielefeld Retired 2011-11-13 08:25:10 UTC
Do you have any information what change in Master did the fix?
Comment 9 Björn Michaelsen 2011-12-23 13:25:22 UTC
Since all new unconfirmed bugs start in state UNCONFIRMED now and old unconfirmed bugs were moved to NEEDINFO with a explanatory comment, all bugs promoted above those bug states to NEW and later are automatically confirmed making the CONFIRMED whiteboard status redundant. Thus it will be removed.