Description: FILEOPEN ODT: Slow file opening compared to LibO 4.4.6.3. (but hard to pin down because of the SAXParseException issue (bug 99227) Steps to Reproduce: 1. Open attachment 124282 [details] (bug 99227) Actual Results: File opening takes around 14 seconds Expected Results: LibO 4.4.6.3 opens the file in around 5 seconds Reproducible: Always User Profile Reset: No Additional Info: Found in Version: 5.4.0.0.alpha0+ Build ID: 53edf60c4ce6ed32f87471e018878c40b788005a CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-12-18_06:57:59 Locale: nl-NL (nl_NL); Calc: CL but not in: Versie: 4.4.6.3 Build ID: e8938fd3328e95dcf59dd64e7facd2c7d67c704d Locale: nl_NL User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Yep, a bit slower. Arch Linux 64-bit, KDE Plasma 5 Version: 5.4.0.0.alpha0+ Build ID: db9aec4520766c87a09d4cb0238ed06ebaeaaeeb CPU Threads: 8; OS Version: Linux 4.8; UI Render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on December 18th 2016
To repeat https://bugs.documentfoundation.org/show_bug.cgi?id=99227#c17 : attachment 129777 [details] contains debug from procdump dump, if of any use
Working on debian-stretch I observe in the bibisect-50max repository that LibreOffice opened the file in about 11 seconds up to the error message introduced in s-h ebf767ee. The latest version in that repository also displays the error message. Within the daily linux dbgutil bibisect repository, my oldest version (2016-05-26) takes about 1 minute 29 seconds to open the file. I conclude that the slowness came into LibreOffice sometime between 2015-01-22 and 2016-05-26. I am leaving keyword bibisectRequest in the hope that somebody can be more helpful than I have been.
Already slow in 5.0.6.3 and 5.1.0.3 / Windows 7. Giver errors on import in 5.0.0.5. I'll go with notBibisectable.
** 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! Warm Regards, QA Team MassPing-UntouchedBug
I got 16 sec in Версия: 6.2.0.1 (x64) ID сборки: 0412ee99e862f384c1106d0841a950c4cfaa9df1 Потоков ЦП: 4; ОС:Windows 10.0; Отрисовка ИП: GL; VCL: win; Локаль: ru-RU (ru_RU); UI-Language: ru-RU Calc: threaded still repro but are you sure that in LO 4.4 this file opens full correct?
it takes real 0m9,624s user 0m9,270s sys 0m0,278s in Version: 6.3.0.0.alpha0+ Build ID: 3b518953a8141b0d5043c2f3996a92956fdc3a47 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded which seems reasonable in an 7 years old computer. I think we can close this as a RESOLVED WORKSFORME
(In reply to Xisco Faulí from comment #7) > it takes > > real 0m9,624s > user 0m9,270s > sys 0m0,278s > > in > Probably depending on the backend. It's certainly slower on Windows Version: 6.3.0.0.alpha0+ Build ID: 8d45d5ee399d0148672e79c379f5d29e1c8ba6f3 CPU threads: 4; OS: Windows 6.3; UI render: GL; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-03-29_01:02:58 Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL @but are you sure that in LO 4.4 this file opens full correct? -> No clue, didn't check
(In reply to Telesto from comment #8) > (In reply to Xisco Faulí from comment #7) > > it takes > > > > real 0m9,624s > > user 0m9,270s > > sys 0m0,278s > > > > in > > > Probably depending on the backend. It's certainly slower on Windows > Version: 6.3.0.0.alpha0+ > Build ID: 8d45d5ee399d0148672e79c379f5d29e1c8ba6f3 > CPU threads: 4; OS: Windows 6.3; UI render: GL; VCL: win; > TinderBox: Win-x86@42, Branch:master, Time: 2019-03-29_01:02:58 > Locale: nl-NL (nl_NL); UI-Language: en-US > Calc: CL > > @but are you sure that in LO 4.4 this file opens full correct? > -> No clue, didn't check Please, be accurate when talking about timing. certainly slower doesn't help...
> Please, be accurate when talking about timing. certainly slower doesn't > help... 16 seconds. same as comment 6
12 seconds in Versión: 6.2.2.2 Id. de compilación: 2b840030fec2aae0fd2658d8d4f9548af4e3518d Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; VCL: win; Configuración regional: es-ES (es_ES); Idioma de IU: es-ES Calc: threaded in the same computer running Win 7 in a VM. @Telesto, please measure the timing in 4.4.6.3 with the same computer and add the attach the pdf export from 4.4.6.3 and master so see if anything changed...
Dear Telesto, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Telesto, 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 MassPing-NeedInfo-FollowUp
Working with bibisect-linux-64-6.4 repository s-h c4d760b9 (2019-10-28) on debian-buster, I observe the following cumulative CPU time to (*) reach approximately 0 CPU usage after opening the file, (*) position to end of document (*), close the document. VCL:x11 VCL:x11 VCL:gtk3 ------- ------- -------- open file 7.13 6.95 9.53 <ctrl>+<End> 7.79 7.53 9.69 <ctrl>+W 8.06 7.89 10.17 I shall leave it to Telesto to change bug status, if he wishes.