Bug 93341 - loading calc is slow
Summary: loading calc is slow
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: All Linux (All)
: high minor
Assignee: Not Assigned
Depends on:
Blocks: Calc-Images
  Show dependency treegraph
Reported: 2015-08-11 03:20 UTC by Ivor O'Connor
Modified: 2017-03-01 10:37 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

This small file takes minutes to load! (18.33 KB, application/vnd.oasis.opendocument.spreadsheet)
2015-08-11 03:20 UTC, Ivor O'Connor
valgrind log of opening libre with file, saving one change, and exiting (971.68 KB, text/x-log)
2015-08-11 21:06 UTC, Ivor O'Connor

Note You need to log in before you can comment on or make changes to this bug.
Description Ivor O'Connor 2015-08-11 03:20:41 UTC
Created attachment 117820 [details]
This small file takes minutes to load!

I upgraded LO from whatever came with Mint 17.2 XFCE 64 bit to LO-5.0. Now however loading or even saving a file takes minutes despite having 32GBs, SSDs, RAM disk, and an I7-4910 cpu running at top speed. The spreadsheet is very small. It loads much faster on an old I3 laptop running off an SSD with LO-4.x than it does with 5.0. However if I run it from a ram disk and start it with "sudo nice --10 libreoffice5.0 --calc PriceLogDellM6800.ods" the speed is much better. Is there perhaps a problem with the latest version of 5.0 on loading this spreadsheet? I've looked at the log at "~/.config/libreoffice/4/user/uno_packages/cache/log.txt" but nothing of interest is there. Just times the program was closed. Is there something in the spreadsheet LO-5 doesn't handle correctly or is this a user bug of some sort. If a user bug how do I figure out what is causing it to hang for so long?
Comment 1 Joel Madero 2015-08-11 03:34:47 UTC
A bibisect and a valgrind would be really awesome here.



I can confirm:
Ubuntu 15.04 x64
LibreOffice (broken)
LibreOffice (works)


Marking as:
Minor - can slow down professional quality work but will not prevent it;
High - regression, would be nice to figure it out. Although we only have one test case it may indicate larger issues.
Comment 2 MM 2015-08-11 20:33:31 UTC
Unconfirmed with v5.0.0.5 under mint 17.2 x64.
Unconfirmed with v5.0.0.5 under ubuntu 15.04 x64.

File loads in seconds (not minutes), just like in v4.4.5.2 and earlier.
Comment 3 Ivor O'Connor 2015-08-11 21:06:38 UTC
Created attachment 117845 [details]
valgrind log of opening libre with file, saving one change, and exiting

I installed valgrind and then issued this command:
sudo nice --10 libreoffice5.0 --calc --valgrind PriceLogDellM6800.ods  >& /tmp/valgrind.log

Once opened I changed one cell, issued a save, then exited.

It's the first time I used valgrind and if I used it incorrectly please let me know how to use it correctly.

Comment 4 Joel Madero 2015-08-11 21:15:29 UTC
I'm not exactly sure what we use for "have-valgrind" but I'm just adding "have-backtrace" to indicate that there is some guidance as to what's going on.

@Ivor - thanks 1000x over for doing the valgrind. We'd love to see you join QA over at http://webchat.freenode.net/?channels=libreoffice-qa
Comment 5 Matthew Francis 2015-08-16 11:51:33 UTC
It could be hard to prove, but I have a suspicion this may be a duplicate of e.g. bug 42742 or some related issue.

The attached spreadsheet contains external images - e.g. the "RAM" sheet contains
and others. There are known issues with loading external images - especially if something causes the image to load slowly (e.g. DNS issues) or the remote site to silently not connect at all.

I also don't see any significant change in speed from 4.4 onwards. With some slight variation, it loads in under 2 seconds each time. Unfortunately that means it still needs someone who can actually reproduce this to look at it further and prove or disprove the above.
Comment 6 Timur 2015-08-17 16:44:29 UTC
Couldn't reproduce. Mint 17.2 Cinnamon/XFCE 64 bit with LO-5.1 dev.
Comment 7 Robinson Tryon (qubit) 2015-12-14 05:32:47 UTC Comment hidden (obsolete)
Comment 8 Joel Madero 2015-12-20 06:56:47 UTC
I've spent a bit more time with this one and I'm throwing it back to UNCONFIRMED.

I just tested 5.0, 5.2, and 3.3 and get basically the same behavior for each. I'm not sure what I confirmed before but I don't see anything taking minutes....everything takes about 5-10 seconds.
Comment 9 Markus Mohrhard 2016-04-08 02:12:43 UTC
Comment on attachment 117845 [details]
valgrind log of opening libre with file, saving one change, and exiting

valgrind is the wrong tool. callgrind(which is part of the valgrind tool suite) is the only one that makes sense here.
Comment 10 Buovjaga 2016-04-23 15:56:01 UTC
Opens instantly. Please retest.

Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.

Arch Linux 64-bit, KDE Plasma 5
Build ID: 334599030e7b45153107a3075f9049a7463aac80
CPU Threads: 8; OS Version: Linux 4.5; UI Render: default; 
Locale: fi-FI (fi_FI.UTF-8)
Built on April 22nd 2016
Comment 11 Bojan 2016-08-04 05:53:49 UTC Comment hidden (off-topic)
Comment 12 Bojan 2016-08-04 10:12:47 UTC Comment hidden (off-topic)
Comment 13 Buovjaga 2016-08-04 10:48:25 UTC Comment hidden (off-topic)
Comment 14 QA Administrators 2017-01-31 00:29:51 UTC Comment hidden (obsolete)
Comment 15 QA Administrators 2017-03-01 10:37:09 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team