Created attachment 81128 [details]
The test file
The file attached is viewed fine in Microsoft word viewer but when open in libre office I get a message "general input/output" error.
I have been testing this file and confirm that I get the message 'General input/output".
The processor is running at 100% and opening the file take more than 2 minutes to reach the error message.
However, when pressing retry the file is opening.
On low speed processor (netbook) it can took 2 times to press to retry to get result. Note that formatting of the table looks strange
*** This bug has been marked as a duplicate of bug 67699 ***
It's not a duplicate of bug 67699, as the latter is a regression of 4.1, while this bug was reported against 4.0. Also bug 67699 is fixed as of 184.108.40.206, while this bug still reproducible. Tested with Fedora 19 (64-bit) in VirtualBox + lowered Execution Cap (to emulate slow processor). However it opens fine on my host machine (LO 220.127.116.11 under Ubuntu 13.04 64-bit).
(In reply to comment #4)
You are absolutely right. Still reproducible under Ubuntu. I should have been more careful.
*** Bug 70537 has been marked as a duplicate of this bug. ***
Caused by http://cgit.freedesktop.org/libreoffice/filters/commit/?id=2e9f9d82110342601d28408ae77d63b673993ebe. There is always 60 seconds timeout before the error message is displayed. So if the document is not so large and the processor is not so slow, then it opens without any error. For more information, see Bug 35543.
*** Bug 61546 has been marked as a duplicate of this bug. ***
Reproduce with Version: 18.104.22.168.0+
Build ID: 5536b127a105123de6f64dcf8f53dfa277faef3c
TinderBox: Win-x86@42, Branch:libreoffice-4-3, Time: 2014-07-16_10:15:31
Windows XP SP3.
Set platform to all.
I first noticed this bug behaviour when I was trying to open a 100M MS 2003 XML spreadsheet. MSO 2013 opens that file within 5 seconds, but LibreOffice takes forever to load it while using 100% CPU, then finally gives I/O error message.
I was thinking LO failed to load it because of its file size. But after I made the file size much smaller (50M->10M-5M...), LibreOffice still fails to open it (high CPU, error message).
Files with only a few KB size can open with no problem
*** Bug 82264 has been marked as a duplicate of this bug. ***
Hi all, I have the exact problem.
LO Calc 22.214.171.124
I thouught, the problem is the XML format, but it's the size.
Strange thing is, that this bug says, it!s been fixed long time ago...
Another strange thing is, that Calc can save such file just fine.
I have just tried to create large 10Mb spread sheet, save it as XML file, which works fine. Then when you try to open it, it crashes....
Just to clarify: This "General I/O error" message is not a bug but a feature - see bug 35543 comment 20. It will appear every 60 seconds *anyway*, a user just need to click "Retry" to continue the import process. The real bug here is the wrong text of that message.
OK, I get the point, but in that case, why it takes 5 minutes to open 10Mb file? (5x times click retry)
Should I write bug on that?
(In reply to comment #15)
> OK, I get the point, but in that case, why it takes 5 minutes to open 10Mb
> file? (5x times click retry)
XSLT processing is slow, it's not related to LO. Try it yourself from the terminal:
$ xsltproc --output output.fods /opt/libreoffice4.3/share/xslt/import/spreadsheetml/spreadsheetml2ooo.xsl input.xml
> Should I write bug on that?
OK, I get the point again. So the solution is not to use XML, but other format.
Thanks for clearing that out.
(In reply to Comment # 16
> XSLT processing is slow, it's not related to LO. Try it yourself from the
Yes, XSLT processing might be slow. I'm not sure that is a sufficient
Excel manages to open such files in a fraction of a second where
LibreOffice takes minutes. You might argue that these files are not very
common and therefore it's not worth fixing this, but from a user's point of
view, it just seems excessively slow.
I agree that fixing the message will be an improvement, because at the
moment there's no indication that clicking on retry is something that is
likely to help.
(In reply to comment #18)
> Yes, XSLT processing might be slow. I'm not sure that is a sufficient
This is a sufficient answer, because we don't have a real filter for those types, just this horrible XSLT stuff. There is nothing better currently.
> You might argue that these files are not very common and therefore it's not
> worth fixing this
I didn't say that (and BTW such files are more common than you might think). The point here is that there is no way to "fix" this like any other bug, instead someone needs to create a whole new filter for those types (which is not a trivial task). And just like any other feature request we have, someone needs to be interested enough to work on this.
Anyway this discussion is out of scope for this particular bug, because the error message in question is not specific to one particular format.
I can open the attach WordML 2003 file fine with LibreOffice 126.96.36.199 (on a quad-core machine though).
The XSLT filter has a built-in timeout that should prevent libreoffice from handing indefinitely in case the filter takes to long. With large files on slower machines that timeout might prevent loading the file even though the filter would eventually finish importing.
The import and export filters for Office 2003 XML are suboptimal an would need a rewrite in order to support a larger feature set or larger files.
If at all possible, save your files to OOXML and import those files to LibreOffice.
I will take the time to look at the problem, but it's very likely I will not be able to fix it.
*** Bug 95334 has been marked as a duplicate of this bug. ***
*** Bug 97472 has been marked as a duplicate of this bug. ***
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Build ID: d1b41307be3f8c19fe6f1938cf056e7ff1eb1d18
CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win;
Locale: ru-RU (ru_RU); UI-Language: en-US
Opening of attached file takes 15 sec on Core i3-3120 (2,5GHz) and I didn't see any error message
Xisco, I'm not sure, WFM or not?
Well - the Excel 2003 XML format is now read by a new filter based on orcus  ; which is why the bugdoc is opened much faster, and no wrong messages would happen.
But the title of the bug ("Wrong message shown when opening large file using XSLT filter") is very precise; and given that we still have some XSLT-based import filters, it could stay open. Well - IMO; no strong opinion though.
(In reply to Mike Kaganski from comment #25)
Sorry - the file in question is not the Excel 2003 XML. Sorry for the noise.
I can confirm, that opening large XLS XML files works. The speed is comparable to MS Excel. I thing this bug can be closed.