Bug 53653 - FILEOPEN: Attempting to open Very Large Excel Spreadsheets CRASH Calc.
Summary: FILEOPEN: Attempting to open Very Large Excel Spreadsheets CRASH Calc.
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: Other All
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Reported: 2012-08-17 18:24 UTC by ori
Modified: 2013-07-08 21:21 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description ori 2012-08-17 18:24:32 UTC
Problem description: When I attempt to open large (~13MB or greater) excel spreadsheets, Calc first becomes very busy; CPU activity maxes out; memory usage is great but not 100%.  After a long lock up, system diagnostics indicate that libreoffice is waiting for something to happen even as the CPU keeps churning.  Then libreoffice crashes.  When libreoffice is restarted, any attempt to "recover" starts the crash all over again.  My work around has been to open the Excel sheets on another computer using Gnome's Gnumeric.  Gnumeric opens the Excel sheets instantaneously; then I convert them to open document .ods files, whereafter I can open them using libreoffice calc with all functionality, but without the speed of operations using Gnumeric.  

Steps to reproduce:
1. Attempt to open any very large Excel spreadsheet.

Current behavior: As described.

Expected behavior: Easy to open large Excel sheets, and rapid operation of sheet functions.

Platform (if different from the browser): I am using libreoffice Version (Build ID: 932b512) installed from the rpms on either Slackware 13.37 or 13.31.  
Browser: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20120314 Firefox/3.6.28
Comment 1 Julien Nabet 2012-08-17 22:04:09 UTC
Could you attach the file here http://wiki.documentfoundation.org/QA/Bugzilla-Attachments so we can try to reproduce?
Comment 2 Rainer Bielefeld Retired 2012-08-19 09:09:15 UTC
Same as "Bug 53698 - FILEOPEN particular large .xlsm causes CRASH"?
Comment 3 ori 2012-08-19 18:02:50 UTC
(In reply to comment #1)
> Could you attach the file here
> http://wiki.documentfoundation.org/QA/Bugzilla-Attachments so we can try to
> reproduce?

Julien, unfortunately the spreadsheets I have encountered the problem on are all acquired under contract, and are highly confidential.  Looking at Rainer Bielefeld's comments on Bug #53698, I note that my spreadsheets are all highly formatted.  

I will test on other similarly large, but unformatted .xls spreadsheets and get back to you with the results.

I think it is significant though that Gnumeric opens them with blinding speed, much faster even than Excel does.  If the Spreadsheet group knows anything about the structure of Gnumeric, they may find a clue.
Comment 4 daniel.schaaaf 2012-09-13 09:31:13 UTC
Is this bug really related to big Excel files, or just to big files in general? I am working with huge Calc files myself and I experience frequent crashes, probably due to memory usage of Calc.

Here is a document from another bug report: https://bugs.freedesktop.org/attachment.cgi?id=63612

Make several copies and open them one by one. On my computer with 4 GB RAM and LibreOffice 3.5 and 3.7alpha0, I can open about six copies, and the seventh with crash LibreOffice instantly! The actual number of copies probably depends on what else is eating up RAM on your machine.
I suspect that memory problems also arise from smaller documents when one works with them for some time.
This instant crash also happened on my 8 GB machine, and I am not sure if LibreOffice used up all the RAM before it crashed, or if it ran into problems earlier.
Comment 5 QA Administrators 2013-05-29 14:00:05 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team
Comment 6 QA Administrators 2013-07-08 21:21:50 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO