Bug 93181 - FILEOPEN: crash opening large XLSX
Summary: FILEOPEN: crash opening large XLSX
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.0.0.5 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2015-08-06 07:55 UTC by Rolf Eder
Modified: 2015-09-15 10:44 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
screenshot with crash on 5.0.0.5 and working in 4.4.5.2 (background) (358.55 KB, image/png)
2015-08-06 07:55 UTC, Rolf Eder
Details
crash report from 5.0.0.5 running OS X 10.10.4 (24.67 KB, application/zip)
2015-08-06 07:57 UTC, Rolf Eder
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rolf Eder 2015-08-06 07:55:59 UTC
Created attachment 117702 [details]
screenshot with crash on 5.0.0.5 and working in 4.4.5.2 (background)

Dear LibO team,

yesterday we found a xlsx file that opened in LibO 4.4.5.2 but now crashes in ver 5.0.0.5. Tested on Win 7, Win 8.1 and OS X 10.10. The file is quite large and contains confidential data so I cannot post it here. Since I do not know which part of the data causes the crash I cannot omit the confidential data or simply exchange it with anonymous content either. How can I help to debug anyway?

I enclosed to files: 

Screenshot with the error running in a win 8.1 environment and a copy of the file opened in 4.4.5.2 on an TS (win2k12r2) in the background. The German error msg may be translated as "general IO error".

Archive with crash report from LibO 5.0.0.5 running OS X 10.10.4 and FILEOPEN of a copy of the same file. I do not know how to create this verbose content in the Win environment.
Comment 1 Rolf Eder 2015-08-06 07:57:13 UTC
Created attachment 117703 [details]
crash report from 5.0.0.5 running OS X 10.10.4
Comment 3 Rolf Eder 2015-08-06 09:42:27 UTC
Hi raal,

I tried WinDBG and procdump following the instructions in the Wiki but neither tool caught the crash.

Maybe "crash" is the wrong word: After the error msg appears (see screenshot in first attachment) you can close the msg and LibO continues. So running Win LibO does not freeze or closes (crashes) - but the file does not load. Running OS X LibO really crashes opening the file (see report in second attachment).

Anything else I can add to solve this bug?

Regards
Rolf
Comment 4 Rolf Eder 2015-08-11 07:55:11 UTC
FILEOPEN of the specific XLSX is working in LibO 5.0.0.5 running Ubuntu 14.04.2 LTS.

FILEOPEN still fails in LibO 5.0.1.1 running OS X 10.10.4

So the regression affects only Win and OS X.
Comment 5 steve 2015-08-11 12:45:02 UTC
Rolf, could you make a copy of that file, sanitize the data and attach the problematic file? This should make testing and reproducing a lot easier.
Comment 6 Rolf Eder 2015-08-11 13:31:08 UTC
Steve,

I would love to sanitize the data and publish the file here. But we are talking about a 9 MB file with more than 100 sheets and approx 400,000 cells, tons of formulae and charts. Any suggestions how-to?

Regards
-- 
Rolf
Comment 7 raal 2015-08-14 07:46:49 UTC
(In reply to Rolf Eder from comment #6)
> Steve,
> 
> I would love to sanitize the data and publish the file here. But we are
> talking about a 9 MB file with more than 100 sheets and approx 400,000
> cells, tons of formulae and charts. Any suggestions how-to?

Hi, look here, hope it helps.
https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F
Comment 8 Rolf Eder 2015-09-15 09:53:59 UTC
Rechecked the problematic XLSX with RC 5.0.2.1 and now it opens OK.

In fact OX X opens the file ten times faster than LibO running Win81. Nevertheless works for me. You may close this bug.
Comment 9 raal 2015-09-15 10:44:02 UTC
(In reply to Rolf Eder from comment #8)
> Rechecked the problematic XLSX with RC 5.0.2.1 and now it opens OK.
> 
> In fact OX X opens the file ten times faster than LibO running Win81.
> Nevertheless works for me. You may close this bug.

Thanks, closing