Bug 69114 - Some exported XLS files (using matrix formulas) will crash in Excel
Summary: Some exported XLS files (using matrix formulas) will crash in Excel
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.1.1.2 release
Hardware: All All
: high major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisectRequest, regression
Depends on:
Blocks:
 
Reported: 2013-09-08 19:27 UTC by Christian Fries
Modified: 2015-12-17 07:30 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Folder containing ODS version of test sheet and two XLS exports (12.22 KB, application/zip)
2013-09-08 19:27 UTC, Christian Fries
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Fries 2013-09-08 19:27:54 UTC
Created attachment 85449 [details]
Folder containing ODS version of test sheet and two XLS exports

Exporting a spreadsheet to XLS (Excel 97 format), where the spreadsheet contains a matrix formula, will result in a sheet, which will likely crash Excel (here Excel 2013).

The problem does not appear with OpenOffice 4.0 (and with earlier versions of LibreOffice).

The problem is 100% reproducible (and a big one for me, since I have to switch to OpenOffice or earlier Versions of LibreOffice ;-).

To reproduce:

1. Open the attached file LibreOfficeExportXLSBug.ods in OpenOffice and LibreOffice respectively.
2. Export the sheet via "Save as... XLS" using the respective program.
3. Open the exported sheet in Excel 2013 (Windows).
4. Notice that cell I17 looks different depending on whether the sheet was exported from LibreOffice or OpenOffice.
5. Select cell I16, click in the formula and press CTRL-SHIFT-ENTER (the command to calculate the formula).

Result:

a) Excel will crash for the sheet exported with LibreOffice.
b) Excel will work as expected for the sheet exported with OpenOffice.


For your convenience, my attachments also contains the two different versions of the XLS resulting from export using OpenOffice and LibreOffice respectively.
Comment 1 Christian Fries 2013-09-08 20:18:44 UTC
Version info:

The problem exists in LibreOffice 4.1.1(.2) (current download at LibreOffice.org)
The problem does not exist in LibreOffice 4.0.5
Comment 2 Joel Madero 2013-09-09 03:58:32 UTC
I can confirm that with your test case MS Office 2010 crashes but the problem is fixed in LibreOffice 4.2 master build. You can confirm this here: 

http://dev-builds.libreoffice.org/daily/master/Win-x86@6-debug/

Also you can test 4.1 daily build which is here:
http://dev-builds.libreoffice.org/daily/libreoffice-4-1/Win-x86@6-debug/

I haven't tested 4.1 daily but I know 4.2 is fixed. So marking as WFM

If it's still a problem in 4.1 daily let me know and we'll figure out what to do. Hopefully it's just fixed in 4.1 daily and then you can expect a fix with the next release of 4.1.x


Thanks!
Comment 3 Christian Fries 2013-10-12 16:12:23 UTC
I had this problem again today with a fresh install of 4.1.2.3 (current and very new version).
Comment 4 Christian Fries 2013-10-12 16:13:05 UTC
PS: I am using MacOS and the daily build directory is often empty...
Comment 5 Joel Madero 2013-10-12 16:51:15 UTC
Yes indeed - it seems like the patch never found it's way into 4.1. I'm going to mark this as NEW and add Markus to see if he can help locate what fixed it with 4.2.
Comment 6 Christian Fries 2013-10-25 14:57:21 UTC
I just checked LO 4.1.3.1 from the web page. It also has this problem.
Comment 7 Joel Madero 2013-10-25 15:03:04 UTC
Indeed it will until you see "target 4.1" in the whiteboard here - until then you can assume we haven't located the patch which fixed it in 4.2
Comment 8 Markus Mohrhard 2013-10-30 22:34:48 UTC
Honestly I have no idea. Maybe some parts of Kohei's rework. A bibisect identifying the commit is necessary if there is the need for a backport. Otherwise I suppose we can close this bug.
Comment 9 Joel Madero 2013-10-31 02:37:15 UTC
Unfortunately bibisect isn't very useful - surprisingly enough it always works fine from bibisect package throughout . . . just tested again on 4.1.2.3 release and it's still broken. That being said without a bibisect we just can't locate the code (and even if we could it would take an immense amount of time). So, ultimately this will be fixed shortly (upon release of 4.2). Alpha 1 is being released in just a week or so, you can verify that it's fixed in it. 

Closing as WFM
Comment 10 Robinson Tryon (qubit) 2015-12-17 07:30:42 UTC
Migrating Whiteboard tags to Keywords: (bibisectrequest)
[NinjaEdit]