Issue 123431 - Very slow to close, no editing
Summary: Very slow to close, no editing
Alias: None
Product: Calc
Classification: Application
Component: save-export (show other issues)
Version: 4.0.1
Hardware: PC Windows, all
: P3 Major (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2013-10-06 04:48 UTC by MotherM
Modified: 2013-11-15 02:40 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Calc spreadsheet 5 cols of data, 5 cols of =SUM x 6000 rows (499.05 KB, application/vnd.oasis.opendocument.spreadsheet)
2013-10-08 09:21 UTC, MotherM
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description MotherM 2013-10-06 04:48:47 UTC
A particular spreadsheet takes 100 seconds to close, even if no editing is done. For the whole 100 seconds soffice.bin consumes a constant 25% of the CPU.  This issue appeared with version 4.0.0 and continues in 4.0.1.
The spreadsheet has around 7000 rows x 14 columns.  Five of the columns contain =SUM($E$5:E6912)
Comment 1 Edwin Sharp 2013-10-06 05:04:05 UTC
Please attach spreadsheet.
Comment 2 MotherM 2013-10-08 09:21:19 UTC
Created attachment 81725 [details]
Calc spreadsheet 5 cols of data, 5 cols of =SUM x 6000 rows
Comment 3 Edwin Sharp 2013-10-08 09:42:45 UTC
Thank you.

confirmed with
AOO410m1(Build:9750)  -  Rev. 1525015
Win 7
Comment 4 alahanco 2013-11-15 02:40:59 UTC
Alan Hancock [November 14, 2013]
AOO401m5(Build:9714)  -  Rev. 1524958
Windows 7

I was able to reproduce the bug by doing the following:

1. Download provided spreadsheet.
2. Open the spreadsheet without altering.
3. Close the spreadsheet, keeping track of time lapsed.

I recorded a lapse of 45 seconds required for the spreadsheet to close. During this time, the process soffice.bin *32 consumes 25% of my CPU.

I followed up to this report by deleting all but one of the columns including an =SUM function. The result was that closing the spreadsheet took 10 seconds and continued to consume 25% of my CPU during that time. I would hypothesize that further tests with additional similar columns would increase lapse time when closing the spreadsheet. This would imply a difficulty with dumping data that requires calculations in the spreadsheet.

This has heavy implications for large spreadsheets that require calculations. I would consider this an alleviated priority because a quality service spreadsheet should be able to exit effectively regardless of the number of calculations.

I see no reasonable workarounds for this issue other than avoiding calculations in a spreadsheet or separating the calculations among several different files.