Issue 124058 - Writer crashes when opening the attached file (2.docx)
Summary: Writer crashes when opening the attached file (2.docx)
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: open-import (show other issues)
Version: 3.4.0 Beta (OOo)
Hardware: All All
: P3 Normal (vote)
Target Milestone: 4.1.0
Assignee: Oliver-Rainer Wittmann
QA Contact:
URL:
Keywords: crash, regression
Depends on:
Blocks:
 
Reported: 2014-01-19 20:53 UTC by Andrea Pescetti
Modified: 2017-05-20 10:35 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: 4.1.0-dev
Developer Difficulty: ---

Attachments
2.docx (120.88 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2014-01-19 20:53 UTC, Andrea Pescetti 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Andrea Pescetti 2014-01-19 20:53:11 UTC 
Created attachment 82319 [details]
2.docx

The attached DOCX file (possibly generated with Pages) opens with OpenOffice.org 3.3.0 (even though the layout is quite broken) but crashes OpenOffice 4.0.1.

File is discussed, in Italian, at
https://forum.openoffice.org/it/forum/viewtopic.php?t=5158&p=24840#p24840
Comment 1 Regina Henschel 2014-01-19 20:59:26 UTC 
I confirm the crash with my Windows debug build of AOO410m1(Build:9750)  -  Rev. 1554790.
The debug build shows this error messages:
Error: no context of this type available From File C:/AOO_2013_10_08_v41/trunk/main/writerfilter/source/dmapper/DomainMapper_Impl.cxx at Line 325
Error: DomainMapper::attribute() - Id: 9264 / 0x2430 value: 0 / 0x0 From File C:/AOO_2013_10_08_v41/trunk/main/writerfilter/source/dmapper/DomainMapper.cxx at Line 2185
Comment 2 Oliver-Rainer Wittmann 2014-01-20 11:00:11 UTC 
taking over to have a closer look
Comment 3 Oliver-Rainer Wittmann 2014-01-20 11:10:25 UTC 
I can reproduce the crash on my system (Windows 7) with AOO 3.4.0, AOO 3.4.1, AOO 4.0.0 and AOO 4.0.1. I can also reproduce the crash with OOo 3.4.1Beta.
--> adjusting fields:
- "Version" = 'pre 3.4.0' (actually '3.4.0')
- "Latest Confirmation on" = '4.1-dev'
Comment 4 Oliver-Rainer Wittmann 2014-01-20 12:26:28 UTC 
taking over to work on a solution.
Comment 5 Oliver-Rainer Wittmann 2014-01-20 13:19:21 UTC 
Are there further information about the origin of the given document?
I am asking, because just a "save-as" in Microsoft Word 2007 without any editing changes the document in such a way that it can be imported into AOO 4.0.1 (only the image is missing).
Comment 6 SVN Robot 2014-01-20 17:54:32 UTC 
"orw" committed SVN revision 1559791 into trunk:
124058: *.docx import - check existence of Style before accessing it
Comment 7 Oliver-Rainer Wittmann 2014-01-20 17:57:02 UTC 
fix the crash on trunk for next release
Comment 8 Andrea Pescetti 2014-01-26 13:34:26 UTC 
Thank you Oliver, I confirm the file opens with no crash with the current trunk.

The file was produced with Pages (even though they are unsure about the version), so this issue is very likely the same as https://issues.apache.org/ooo/show_bug.cgi?id=124106 

Note that in both cases we now avoid the crash, but the import quality is very bad: namely, it seems you get one line per page, aligned to the right and with double stroke. Following up on bug 124106 since test documents are better in that case.
Comment 9 Oliver-Rainer Wittmann 2014-02-12 16:17:26 UTC 
closing to be able to reopen
Comment 10 Oliver-Rainer Wittmann 2014-02-12 16:18:17 UTC 
reopening as my code changes causes a crash.
Comment 11 SVN Robot 2014-02-13 09:27:28 UTC 
"orw" committed SVN revision 1567869 into trunk:
124058: correction the formerly provided fix
Comment 12 Oliver-Rainer Wittmann 2014-02-13 09:29:17 UTC 
corrected formerly provided fix on trunk
Comment 13 Andrea Pescetti 2014-02-23 19:50:44 UTC 
I confirm that the test document does not crash with the current trunk. The import is still extremely bad and I can't understand why all text gets the "double stroke" effect, but this is covered in bug 124106.