User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0 Build Identifier: LibreOffice 5.0.3.2 It takes nearly three seconds until the about dialog in any LibreOffice component shows up. This seems slow to me, especially for a computer with a SSD. The problem is trivial but I decided to report it anyway. It occurs since version 5.0. Reproducible: Always Steps to Reproduce: 1. Start any LibreOffice component, e.g. Writer 2. Click "Help" 3. Click "About LibreOffice" Actual Results: 2-3 seconds no response until the dialog is shown Expected Results: Instant showing of the about dialog Locale: de OS: Arch Linux OS is 64bit: yes Reset User Profile?Yes
it takes 1.5 seconds under Win7x64 using LibO 5.0.3.1 and recent 5.1.0.0 daily builds
For me reproducible with LO 5.0.3.2, Win 8.1. It takes around 2 to 2.5 seconds until the About LibreOffice dialog box is opened.
(In reply to tommy27 from comment #1) > it takes 1.5 seconds under Win7x64 using LibO 5.0.3.1 and recent 5.1.0.0 > daily builds it shows up instantly with LibO 4.4.5 so that's a regression and needs bibisecting
Migrating Whiteboard tags to Keywords: (bibisectRequest) [NinjaEdit]
Working in the daily dbgutil repository, I see from `git bisect good` ... e229217b7da6f5d9225edffd69287f33299c8684 is the first bad commit commit e229217b7da6f5d9225edffd69287f33299c8684 Author: Miklos Vajna <vmiklos@collabora.co.uk> Date: Sat Jul 25 05:39:10 2015 +0200 2015-07-25: source-hash-fe88fe6f828597fe2645a20c1a07716216a810c3 :100644 100644 e47729709af478c8bdef5554255c16d44cedc8f5 d8489393443e2bae309b1803ab7dca1228e93ff1 M build-info.txt :040000 040000 8b5dfb113b7f678743a27d4757f6a49316d05d90 c7242ffd226363d7282c112b66a265d1a757e9f5 M opt and from `git bisect log` ... # bad: [c5625a3e1014766a488ca42e986be5dd3efbf051] 2015-11-24: source-hash-e5b3ec9683e4c5761633a1a3c4819a039e796b01 # good: [2b392af9c8f54629e3a3a98a8c92fa5af1c6722f] 2015-05-20: source-hash-90e2dabb8d0bb5382234be776c2ad0e2d5d9e224 git bisect start 'c5625a3' '2b392af' # bad: [a8d19eafb9e195a85359dd8cdc5c46c38295caa0] 2015-08-22: source-hash-79fb61efb847405fa47235002b52ee8efad5e339 git bisect bad a8d19eafb9e195a85359dd8cdc5c46c38295caa0 # good: [c9abefa2facd9d5f2989bbc2138e55970e60c4cd] 2015-07-06: source-hash-64385c7555c6bbb089f3ab8b2a5b623cadd6ee7d git bisect good c9abefa2facd9d5f2989bbc2138e55970e60c4cd # bad: [7b4308803bb448efe4d64dcdea03e9d5be6dde9d] 2015-07-29: source-hash-62e2fae93e8894f73560a30ae1e752cbd4c001ad git bisect bad 7b4308803bb448efe4d64dcdea03e9d5be6dde9d # good: [6e6e48df3b6eb13cf54223cd1ffac16546ec49c2] 2015-07-17: source-hash-14257152b19c08618a107c6eb0f684de11483da8 git bisect good 6e6e48df3b6eb13cf54223cd1ffac16546ec49c2 # good: [1cd3607857e7065cfb54d4ea5ca08c78c0ab83d8] 2015-07-23: source-hash-e92a8b92072284fd7c37d7bb3e1e8fe72a185f35 git bisect good 1cd3607857e7065cfb54d4ea5ca08c78c0ab83d8 # bad: [5e95a5e0e09583fa603470e648dc904825745efa] 2015-07-26: source-hash-11f24bc2f032b31095663cb09ef948eee2c61f49 git bisect bad 5e95a5e0e09583fa603470e648dc904825745efa # bad: [e229217b7da6f5d9225edffd69287f33299c8684] 2015-07-25: source-hash-fe88fe6f828597fe2645a20c1a07716216a810c3 git bisect bad e229217b7da6f5d9225edffd69287f33299c8684 # good: [b28257760a5ff12f099c4c983b6a783cc6de465c] 2015-07-24: source-hash-ba90813d17cf35cfb67585d6f119d3ddb30f5978 git bisect good b28257760a5ff12f099c4c983b6a783cc6de465c # first bad commit: [e229217b7da6f5d9225edffd69287f33299c8684] 2015-07-25: source-hash-fe88fe6f828597fe2645a20c1a07716216a810c3 I am removing keywork bibisecRequest and adding keyword bibisected.
Where can I find this commit? http://cgit.freedesktop.org/libreoffice/core/commit/?id=e229217b7da6f5d9225edffd69287f33299c8684 returns nothing.
Commit e229217 is the id of a binary in the daily debug util bibisect. For the source code, look at the source hash. The range ba90813..fe88fe6 covers 95 commits. (I have yet to learn how to limit `git log` to commits to master. Sigh.)
*** Bug 97224 has been marked as a duplicate of this bug. ***
For me it is not a bug because the current About dialog shows more informations than in previous versions. So it has more data to collect as showed by first "bad" commit. Closing as NotABug and removing regression keyword. Please, feel free to reopen if you disagree. Best regards. JBF
The culprit is this commit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=8cfdd81b70ef37927b40497ffd10034f28335034 These two complex SVG files: - flat_logo.svg (794 KB vs nothing) - about.svg (676 KB vs 15 KB) are the ones that slow down the About dialog. Removing them fixes the problem. Either we use simpler SVG files or PNG files (like for the splash screen). Adding bisected, regression and topicUI keywords.
Adding Cc: to Christian Lohmaier
Adding Christian, since he wasn't CC-ed before. Christian, would it be possible to have PNGs shipped instead of those two big SVG files?
*** Bug 105591 has been marked as a duplicate of this bug. ***
Fixed in 6.0 by this commit: https://cgit.freedesktop.org/libreoffice/core/diff/?id=e1c89b12c94c06309032250da0ac7c84d3f96bb6
By the way, the previous logos (causing this bug) were PNG files encapsulated in SVG, thus their size.
Reopening because newer SVG logos still create a noticeable delay (albeit smaller than before) when opening the about dialog. Using PNG images instead (like e.g. Firefox) would fix it.
Dear [user-name], This bug has been in RESOLVED FIXED status for more than 1 months. If the issue is still reproducible with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/, please report a new issue in https://bugs.documentfoundation.org/enter_bug.cgi providing, if needed, the steps and documents to reproduce it. Thanks for your understanding and collaboration. Closing as RESOLVED FIXED
Created attachment 156344 [details] Optimized about dialog SVG file (fully vectorized) Here's an optimized version of the SVG file that slows down the about dialog. Note that the encapsulated PNG file has been replaced by a proper vector version. Optimized using https://kraken.io/web-interface
Thomas: as Xisco indicated, please create a new bugtracker.