Bug 70537 - FILTER: Bad performance/unable to open 3.3MB Excel XML file
Summary: FILTER: Bad performance/unable to open 3.3MB Excel XML file
Status: RESOLVED DUPLICATE of bug 65980
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.6.4.3 release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-16 14:44 UTC by Michael Wood
Modified: 2013-10-19 18:39 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
The offending file. (2.14 KB, application/x-bzip)
2013-10-18 06:38 UTC, Michael Wood
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Wood 2013-10-16 14:44:58 UTC
Problem description:

When I got the problem file I was running LO 3.6.4.3-3 (as downloaded from www.libreoffice.org).  I then upgraded to 4.1.2.3-3 to see if it would help, but the problem persists.

Calc can't open a spreadsheet generated by another system.  Calc freezes for a long time and eventually pops up an error message that reads:

  General input/output error.
             [Retry] [Cancel]

Retry does not help.

Clicking Cancel results in another error message saying:

  General Error.
  General input/output error.
         [OK]

Excel complains that the format doesn't match the extension (or something like that) and after clicking on OK it opens the file in a fraction of a second.

The file is a plain XML file.  Not an Office OpenXML file.  The first tag looks like this:

<Workbook xmlns="urn:schemas-microsoft-com:office:spreadsheet" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:ns0="http://netcare.co.za/xi/hl7_data" xmlns:o="urn:schemas-microsoft-com:office:office">

Steps to reproduce:
1. Open badperf.xls
2. See CPU spike and Calc freeze for about 1 minute.
3. See I/O error messages.

Current behavior:
Calc freezes for about one minute, using up 100% of one core before displaying an error.
The file does not open.

Expected behavior:
The file opens successfully in a reasonable amount of time.
Operating System: Ubuntu
Version: unspecified
Comment 1 m_a_riosv 2013-10-16 21:12:46 UTC
Hi Michael,
please try to open as:
Microsoft Excel 2003 XML

maybe a similar issue like in this bug:
https://bugs.freedesktop.org/show_bug.cgi?id=70100
Comment 2 Urmas 2013-10-16 23:35:09 UTC
What are the dimensions of your worksheets?
Comment 3 Michael Wood 2013-10-17 13:38:39 UTC
Hi

(In reply to comment #1)
> Hi Michael,
> please try to open as:
> Microsoft Excel 2003 XML

This had a similar effect.  I did the following:

1. Started Calc
2. Clicked on the File menu and chose Open
3. Selected the "badperf.xls" file
4. Expanded "File type" and chose "Microsoft Excel 2003 XML"
5. Clicked Open

At this point the Loading progress bar at the bottom showed about 50%, Calc started using 100% of one of my CPU cores, and after a while it popped up the "General input/output error." dialog with Retry and Cancel buttons.  Clicking Retry actually loaded the spreadsheet immediately.  I am sure I tried that before when running 3.6 and it did not work, but I had not yet tried that with 4.1.

> maybe a similar issue like in this bug:
> https://bugs.freedesktop.org/show_bug.cgi?id=70100

I don't think so.  I had this problem with 3.6 and tried upgrading to 4.1 to see if it made a difference.  70100 says it worked for them in 4.0.  Also, Writer never seems to try to open this file.
Comment 4 Michael Wood 2013-10-17 13:41:09 UTC
(In reply to comment #2)
> What are the dimensions of your worksheets?

There are 5 sheets.

sheet 1: cols=2, rows=57
sheet 2: cols=4, rows=3664
sheet 3: cols=4, rows=3377
sheet 4: cols=3, rows=9907
sheet 5: cols=2, rows=949
Comment 5 Julien Nabet 2013-10-17 18:13:42 UTC
Michael: would it be possible you attach the file to the bugtracker so we can try to reproduce? (remove any private info if needed since it'll be available to anyone)
Comment 6 Michael Wood 2013-10-18 06:30:08 UTC
(In reply to comment #5)
> Michael: would it be possible you attach the file to the bugtracker so we
> can try to reproduce? (remove any private info if needed since it'll be
> available to anyone)

Hi Julien

Sorry, I thought it was here, because I uploaded it when I filled in the bug submission form!  I will upload it now.
Comment 7 Michael Wood 2013-10-18 06:38:28 UTC
Created attachment 87812 [details]
The offending file.

Contents are anonymised.

I have compressed it with bzip2.
Comment 8 Maxim Monastirsky 2013-10-18 09:10:32 UTC
Opens fine with 4.1.1.2 under Ubuntu 13.04 (64-bit). Looks like an exact duplicate of Bug 65980.

*** This bug has been marked as a duplicate of bug 65980 ***
Comment 9 Michael Wood 2013-10-18 14:17:16 UTC
(In reply to comment #8)
> Opens fine with 4.1.1.2 under Ubuntu 13.04 (64-bit). Looks like an exact
> duplicate of Bug 65980.
> 
> *** This bug has been marked as a duplicate of bug 65980 ***

hmmm...  Strange.

I would not call this a "slow processor":

$ grep -E '^(processor|model name)' /proc/cpuinfo 
processor	: 0
model name	: Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz
processor	: 1
model name	: Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz
processor	: 2
model name	: Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz
processor	: 3
model name	: Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz
processor	: 4
model name	: Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz
processor	: 5
model name	: Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz
processor	: 6
model name	: Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz
processor	: 7
model name	: Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz
Comment 10 Maxim Monastirsky 2013-10-19 18:39:04 UTC
(In reply to comment #9)
> hmmm...  Strange.
> 
> I would not call this a "slow processor":
> 
OK, so in your case it might be caused by a poorly optimized build, or by some slow version of libxslt which bundled with the official build, so the open process exceeds the 60 seconds timeout (as I've explained in Bug 65980 comment 7). And indeed I can reproduce that error with the official build (from libreoffice.org), on the same machine where it opens fine using the build from PPA.