Bug 142572 - kspread using up almost all memory and cpu with ods opendocument spreadsheet
Summary: kspread using up almost all memory and cpu with ods opendocument spreadsheet
Status: RESOLVED DUPLICATE of bug 59510
Alias: None
Product: calligrasheets
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Calligra Sheets (KSpread) Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-05 22:22 UTC by Sam Roberts
Modified: 2007-04-16 16:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
This is the spreadsheet that causes the problem, bzipped. (12.83 KB, application/octet-stream)
2007-03-05 22:24 UTC, Sam Roberts
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sam Roberts 2007-03-05 22:22:28 UTC
Version:           1.6.2 (using KDE KDE 3.5.5)
Installed from:    Unspecified Linux
OS:                Linux

Trying to open an openoffice spreadsheet, kspread uses ~ 50% cpu and > 90% memory. It is almost impossible to kill, closing the window left the process still running, eventually I managed to killall -9 it, but it took several minutes due to system being unresponsive.

I don't think this is same as similar sounding bugs, the spreadsheet is small (one page), and has no complex formulas, its just a timesheet.

QTime::setHMS Invalid time -1:-1:-1.000

appears for serveral screens.

The spreadsheet was originally excel, imported into ooffice, then saved in native format.

I hope that I will be given the option to upload the spreadsheet in this bug report process.
Comment 1 Sam Roberts 2007-03-05 22:24:21 UTC
Created attachment 19890 [details]
This is the spreadsheet that causes the problem, bzipped.
Comment 2 Stefan Nikolaus 2007-04-16 16:32:00 UTC
Closing. As it works in trunk, the upcoming 2.0. Very slowly, but still. The new QXmlStreamReader could solve the speed issue, but that'd be a lot of work.

Anyways, it's the big document issue.


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