Bug 94792 - Fileopen: performance regression for xlsx with chart (per Comment 4)
Summary: Fileopen: performance regression for xlsx with chart (per Comment 4)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.4.0 release
Hardware: Other All
: medium minor
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords: bibisectRequest, perf, regression
Depends on:
Blocks:
 
Reported: 2015-10-05 15:33 UTC by c.kirbach
Modified: 2017-09-29 08:48 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
gdb information LO 4.4.5.2 (72.85 KB, text/x-log)
2015-10-05 15:33 UTC, c.kirbach
Details
minimum test case (2.15 MB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2015-10-18 08:47 UTC, c.kirbach
Details

Note You need to log in before you can comment on or make changes to this bug.
Description c.kirbach 2015-10-05 15:33:25 UTC
Created attachment 119312 [details]
gdb information LO 4.4.5.2

Infinite loop (100% CPU usage) trying to open Excel file

Cannot provide the Excel as it is confidential but may be able to reduce it to a minimum test case

attaching the gdb diagnose information I tool
Comment 1 Timur 2015-10-05 17:13:33 UTC
Please attach anonymized Excel file (xlsx, xls?)
Please try with the current LO master, for example http://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@70-TDF/current/.
Comment 2 c.kirbach 2015-10-18 08:46:40 UTC

Infinite loop does not happen with lastest LO5 alpha build.
I reduced it to an anonymised minimum test case that I am attaching.
Comment 3 c.kirbach 2015-10-18 08:47:27 UTC
Created attachment 119712 [details]
minimum test case
Comment 4 Timur 2015-10-19 08:48:47 UTC
(In reply to c.kirbach from comment #2)
> Infinite loop does not happen with latest LO5 alpha build.
It doesn't happen with master, LO 5.1+, although it's rather slow to open.
It opens even with 5.0.2.2, but after a "very" long time, so I wouldn't say it's  infinite loop. It was some recent regression in terms of terribly slow opening.
Looks like something is fixed, and future releases 5.0.3 and 4.4.6 should be checked for backport.

I think this bug may be closed as "WorksForMe" but another one should be open for poor performance with the opening. It's a regression from LO 3.4. 
LO 5.1+ took 112 sec in Windows with i7 processor. OO 3.3 and LO 3.3.4 took "only" 27 seconds to open.
Or this bug may be changed to "Fileopen: performance regression for xlsx with chart"
Comment 5 c.kirbach 2015-10-20 15:27:03 UTC
Renaming as suggested by you.


It doesn't happen with master, LO 5.1+, although it's rather slow to open.
It opens even with 5.0.2.2, but after a "very" long time. It was some recent regression in terms of terribly slow opening.
Looks like something is fixed, and future releases 5.0.3 and 4.4.6 should be
checked for backport.
Comment 6 Markus Mohrhard 2016-04-08 02:08:58 UTC
Please don't forget to tag performance problems as they can be easily missed.
Comment 7 Markus Mohrhard 2016-04-18 23:52:43 UTC
(In reply to c.kirbach from comment #5)
> Renaming as suggested by you.
> 
> 
> It doesn't happen with master, LO 5.1+, although it's rather slow to open.
> It opens even with 5.0.2.2, but after a "very" long time. It was some recent
> regression in terms of terribly slow opening.
> Looks like something is fixed, and future releases 5.0.3 and 4.4.6 should be
> checked for backport.

Performance improvements are nearly never backported.
Comment 8 Xisco Faulí 2016-09-20 12:28:26 UTC
Adding keyword 'bibisectRequest'
Comment 9 Xisco Faulí 2017-09-29 08:48:14 UTC
** 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 on a currently supported version of LibreOffice 
(5.4.1 or 5.3.6  https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and 
your operating system, and any changes you see in the bug behavior
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave 
a short comment that includes your version of LibreOffice and Operating System

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)

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: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug-20170929