Bug 92729 - FILESAVE: Calc crashes when saving large files
Summary: FILESAVE: Calc crashes when saving large files
Status: RESOLVED DUPLICATE of bug 89882
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.4.4.3 release
Hardware: x86-64 (AMD64) macOS (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-14 13:34 UTC by Gordon
Modified: 2015-07-14 17:05 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gordon 2015-07-14 13:34:02 UTC
Calc crashes when saving a large ODS file.  This problem started immediately after installing 4.4.4.3.  Versions prior to this work fine.

This bug sounds very similar to bug 89882 (https://bugs.documentfoundation.org//show_bug.cgi?id=89882).

I have the file that causes the problem, however it is filled with private and proprietary information and I can't provide it under the licensing terms.  I'd be happy to help find an alternative example file, if the libreoffice team can help find an alternative.

I've been using Libreoffice for many years.  This particular spreadsheet is for my daily hours and it is very important to my daily time reporting.  Would very much appreciate a fix.

Thanks,
Gordon
Comment 1 Alex Thurgood 2015-07-14 15:38:21 UTC
@Gordon : on the face of it,yes, it does sound similar to bug 89882.
Without the file we are stymied.

I'm pretty certain that there used to be a large-ish test file that was used way back during 3.x development to test performance improvements, sadly, I don't know where that file is, or even how big it was. 

Setting to NEEDINFO pending a file I can use to test
Comment 2 Alex Thurgood 2015-07-14 15:40:42 UTC
There appear to be performance problems affecting recent versions of LO Calc on OSX when multiple recalculations are required, which lead to the spinning beach ball syndrome, and quite possibly, in your case and bug 89882, to OSX scheduler declaring the process "not responding" and killing it.
Comment 3 Alex Thurgood 2015-07-14 16:40:56 UTC
Mac mini Server (mi-2010)
2,66 GHz Intel Core 2 Duo
4 Go 1067 MHz DDR3
NVIDIA GeForce 320M 256 Mo

Tested a 54Mb csv import, then save to ODS, resulting ODS file 15Mb

Import : approx 5 min

Save as ODS : > 10 min, proc maxes out at 100%, OSX thinks that the proc has died and offers to kill it.

No calculations involved.

The test file was provided by Dave Largo on the dev channel
Comment 4 Alex Thurgood 2015-07-14 17:05:25 UTC

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