Bug 106120 - Crash in: SwWriteTable::SwWriteTable(SwTable const *,SwHTMLTableLayout const *)
Summary: Crash in: SwWriteTable::SwWriteTable(SwTable const *,SwHTMLTableLayout const *)
Status: RESOLVED DUPLICATE of bug 105769
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.3.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-21 04:40 UTC by Michael Weske
Modified: 2017-02-21 17:54 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["SwWriteTable::SwWriteTable(SwTable const *,SwHTMLTableLayout const *)"]


Attachments
this is file associated with crash c42697dc-d589-4d83-99d0-2b2389cfd039 (17.68 KB, application/vnd.oasis.opendocument.text)
2017-02-21 04:40 UTC, Michael Weske
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Weske 2017-02-21 04:40:20 UTC
Created attachment 131376 [details]
this is file associated with crash c42697dc-d589-4d83-99d0-2b2389cfd039

This bug was filed from the crash reporting server and is br-c42697dc-d589-4d83-99d0-2b2389cfd039.
=========================================
There is also a second crash (exact same conditions) d086e54e-1820-4acc-8d8f-7c529e5a4d47

I copied the stats screens from a ZHONE 6519-W1 DLS modem and pasted into writer (these stats are as tables.)   Saved as a standard odt and then did "Save As" to save as .docx.  this caused a crash.  The document was recovered and then could be saved as .docx.
Comment 1 Xisco Faulí 2017-02-21 09:24:41 UTC
*** Bug 106121 has been marked as a duplicate of this bug. ***
Comment 2 Xisco Faulí 2017-02-21 09:29:07 UTC
Hi Michael,
Thanks for reporting this.
I tried to copy the tables into a new document and save it as .odt and later as .docx but I couldn't reproduce the crash.
Did you copy the tables from a webpage? if so, could you please provide it?
otherwise, it's important to provide clearer set of step-by-step instructions on how to reproduce the problem.
Comment 3 Timur 2017-02-21 17:54:36 UTC
Same error as Bug 105769, so I close as duplicate. 
Michael, please respond there.

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