Bug 103634 - Crash in: MSWordExportBase::GetItem(unsigned short)
Summary: Crash in: MSWordExportBase::GetItem(unsigned short)
Status: RESOLVED DUPLICATE of bug 112169
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-02 04:12 UTC by Alex Pankhurst
Modified: 2017-09-03 16:15 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["MSWordExportBase::GetItem(unsigned short)"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Pankhurst 2016-11-02 04:12:21 UTC
This bug was filed from the crash reporting server and is br-0902ad70-3517-4c6e-b89d-11924a188b91.
=========================================
Writer crashes when trying to save a large .docx file (originally 28 MB) originally created in Abiword with about 10 high-resolution photos that I was in the process of compressing. There were no problems with the compression process, but when I try to save, LibreOffice crashes with the LibreOffice Document Recovery message. The document recovery process works perfectly, but saving the results in the same format is not possible, even as a new file. It is possible to save as a .odt file, but the same problem occurs when saving the .odt file as a .docx file. (Saving as a .doc file works, though.)
Comment 1 Xisco Faulí 2016-11-02 08:34:19 UTC
Hi Alex,
Thanks for reporting this bug.
Could it be possible that you attach a simplified document where the crash is reproducible?
Regards
Comment 2 Xisco Faulí 2016-11-02 08:57:14 UTC
Setting it to NEEDINFO until the document is provided. Once it's, please set the status back to UNCONFIRMED
Comment 3 QA Administrators 2017-05-02 11:37:13 UTC Comment hidden (obsolete, spam)
Comment 4 QA Administrators 2017-05-31 10:46:36 UTC Comment hidden (obsolete, spam)
Comment 5 Xisco Faulí 2017-09-03 16:15:52 UTC
It seems like a dupe of bug 112169...

*** This bug has been marked as a duplicate of bug 112169 ***