Consider the file at http://www.info.sciverse.com/documents/files/scopus-training/resourcelibrary/xls/title_list.xlsx
It cannot be opened. LibO seems to hang forever. LibO freezes. Other opened documents freeze.
The same happens with Apache Openoffice
Platform (if different from the browser):
Browser: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0
A little update.
Calligra seems able to open it, but not to save it back in ods.
MS office 2007 can save it to ods and read back the ods. However, LibO cannot open the resulting ods.
Another update. LibO in the end seems to be able to open the file. Only it takes 2 hours. This on a rather robust xeon machine. Calligra takes 1 minute. MS Office takes less than 30 seconds.
Requiring a long time to import in some sense could even be acceptable.
However, issues that should be fixed IMHO include:
1) Complete lack of visual feedback while performing this painful import.
2) Once the document is imported, its management should become normal. Conversely, trying to save the document as ods again takes hours. We are talking of about 2-3 orders of magnitude more than MSOffice.
I am changing the title and rising the priority, reflecting the fact that:
1) LibO can actually open the xlsx file provided as a link in the first comment.
2) You can work on the file when it is loaded in memory and edit it.
But... you cannot save the file...
Asking LibO to save *in its own ods format* makes LibO hang apparently forever.
Note: the xlsx file takes about 15 minutes to open on a fast machine. After that, I tried to save the file as ods and the same machine has now been at 100% cpu for about 3 hours, without being able to save.
1) the bug is "new", rather than "unconfirmed" since I have tested on multiple machines and the behavior is consistently reproduced. Furthermore, there is a test file that anyone can download and use for debugging.
2) the priority is "major". As a matter of fact IMHO it should be a "blocker" given that a spreadsheet that lets you open (even if painfully) a document and then lets you edit it, but makes it impossible for you to save your edited document is a quite serious problem.
Weird... copying the tables (with select-all, copy and paste) into a new spreadsheet leads to a document that can be saved.
Hence, apparently, it is the xlsx importer that creates in memory some data structures (formatting stuff? style stuff? who knows) that is lost in copy/paste and that prevents saving.
Today, I saw this behavior with LibreOffice 22.214.171.124 running on 64-bit Windows Server 2008 through Citrix XenApp.
The xlsx file was really simple, just 11 rows. The user then added a bunch of rows and saw a freeze when trying to save it.
I'm afraid I can't publish the testcase, but I can provide it to someone who want to look into this.
I can confirm this issue is valid for the latest release, as I tried the testcase provided on the latest version of LibreOffice on Ubuntu x64.
Changing to blocker as this bug stops adoption in our business.
I wonder if these two bugs are the same: #30770 and #43544
*** This bug has been marked as a duplicate of bug 30770 ***
Please stop marking performance bugs as duplicates. This should only be done by developers after profiling.
This case here has nothing to do with the other bug report.
would you please tell us exactly how much time is needed to load that file on your machine? 2 hours like in comment 2 or 15 minutes like in comment 3.
moreover, the saving issue is only about trying to save in .ods format or even if you keep the .xlsx format?
I propose to change summary notes to:
FILEOPEN - FILESAVE: very slow opening of .xlsx and freeze when saving as .ods
do you agree with it?
has the situation changed in your system using LibO 126.96.36.199?
moved to mab4.2
killed LibO after 5 minutes freeze while trying to load xlsx file with 188.8.131.52 under Win7x64
(In reply to sergio.callegari from comment #3)
> Note: the xlsx file takes about 15 minutes to open on a fast machine. After
> that, I tried to save the file as ods and the same machine has now been at
> 100% cpu for about 3 hours, without being able to save.
changed summary notes to:
FILEOPEN - FILESAVE: very slow opening of .xlsx and freeze when saving as .ods
retested under Win7x64 with an 5 years old laptop
184.108.40.206 --> 3 minutes and 30 seconds
220.127.116.11 --> 1 minute and 30 seconds
18.104.22.168* --> 20 seconds
FILESAVE TO ODS
possible with 22.214.171.124+ (it takes almost 20-30 seconds)
freeze with 126.96.36.199 and impossible to save
did not try with 188.8.131.52
so basically Calc development in 4.4.x is showing promising results on both sides
* Build ID: 268b9c10c9ff27c74678ace99762f28d58d33012
TinderBox: Win-x86@42, Branch:master, Time: 2014-10-02_23:35:24
*** Bug 70867 has been marked as a duplicate of this bug. ***
retested with 184.108.40.206 beta1 (*) under Win7x64
again another improvement
15 seconds to load test .xlsx
50 seconds to save it as .ods with transient freeze
(*) Build ID: 52b7e6bfc848a467baf02c320c29e7f77b92cc93
TinderBox: Win-x86@51-TDF, Branch:libreoffice-4-4, Time: 2014-11-20_23:58:07
moving this from mab4.2 list to mab4.3 list since 4.2.x reached EOL
(This is an automated message.)
Setting priority to highest as this is a MAB. This is part of an effort to make the importance of MAB reflected in priority too.
Can i know what is the latest update on this bug?
can we know by when we can expect a fix for this?
(In reply to tommy27 from comment #15)
> retested with 220.127.116.11 beta1 (*) under Win7x64
> again another improvement
> 15 seconds to load test .xlsx
> 50 seconds to save it as .ods with transient freeze
> (*) Build ID: 52b7e6bfc848a467baf02c320c29e7f77b92cc93
> TinderBox: Win-x86@51-TDF, Branch:libreoffice-4-4, Time: 2014-11-20_23:58:07
> Locale: it_IT
retested with 18.104.22.168.alpha0+ under Win8.1 x64
Build ID: 2a20bf5105181d51aab40bdd4ce8c09615a0e599
TinderBox: Win-x86@42, Branch:master, Time: 2014-12-25_07:55:29
same loading time as in 22.214.171.124 beta1 (15 seconds)
slower .ods saving time (1 minute and 20 seconds vs. 50 seconds)
(In reply to Deepak KS from comment #17)
> Hi Dear,
> Can i know what is the latest update on this bug?
> can we know by when we can expect a fix for this?
We do not give time estimates ever. This is a volunteer community, a volunteer will have to decide on their own that they want to fix the bug. The alternative is that you can submit a patch, find someone to submit a patch, or pay for a fix from a third party. Thanks for your patience and support of LibreOffice.
Load and save is something completely different. Should be two bugs. And load is now fixed in recent versions, right? So, it's about save as ods?
Anyhow, for performance problems, getting profile is really helpful. As described in https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_cachegrind_trace
I agree with Matus.
we should split this into 2 different reports.
having said that, I retested using LibO 126.96.36.199 and 188.8.131.52 alpha (*)
my results are:
FILEOPEN -> 18 seconds
FILESAVE -> 2 minutes and 38 seconds
FILEOPEN -> 58 seconds
FILESAVE -> 5 minutes
so performance got much worse in current master in respect to 4.4.x
(*) Build ID: bb9dad2ef23829b2500c9f99154bca6a8ba7d49a
TinderBox: Win-x86@39, Branch:master, Time: 2015-06-11_23:59:18
Locale: en-US (it_IT)
just retested the FILEOPEN thing
184.108.40.206 and 220.127.116.11 -> 17 seconds
18.104.22.168.alpha1+ (*) -> 65 seconds
so I confirm the severe performance loss in 5.1.x in respect to 4.4.x and 5.0.x
this needs bibisecting or profiling
(*) Build ID: 7d3fa6bae9f7a755eb2d0ca24bf1afd5f3646bb7
TinderBox: Win-x86@39, Branch:master, Time: 2015-08-09_08:38:08
Locale: it-IT (it_IT)
Created attachment 119134 [details]
Slow loading, and even sometimes crashes with a general I/O failure.
I confirm there's a problem with LO 5.
My attached file is loaded in less than 2 seconds with Excel 2003.
The same file opened with LO 5.0.1 or 5.0.2, fails to open with a general I/O error, or opens in more than 2mn15s !
When general I/O error is shown, answering "retry" allows LO to finish loading.
To be honest this bug is a mess. IMHO it should be closed and each of the issues should be reported independently.
@QA team: I doubt that this deserves to be a MAB at all.
Closing as INVALID per expert's advise. Please report separate clean bugs. Also let's keep it off of MAB list.
Migrating Whiteboard tags to Keywords: ( perf bibisectRequest)
I have a similar problem. I am using noew for years LibO for years but since more than a month I connot open my excel or the coressponding LibO Spread sheets. I am at a loss as this are important calculations for me.
The LibO program starts and it seems it tries to open the file but nothing happens. This is also the case with some Writer documents.
I had hopes that it is a bug that is solved with the next update but I have Version: 22.214.171.124 now and the problem persists. What can I do?