Description: LibreOffice is launching slowly with all Interface Languages installed (taking while until splash screen appears) Steps to Reproduce: 1. Install Writer with all languages (or extract the MSI) 2. Launch Writer Actual Results: The splash screen appears within 2-3 seconds low number of Interface languages (say 3) If you install all it takes 9-10 seconds Expected Results: Looks like LibreOffice iterating through all languages on every launch. There must be a way to do this more efficient, as only one language is actually used I get the feeling that LibreOffice 5.0 being slightly faster (but didn't compare the number of languages) Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: 6640d7f405d2970ba2825a9455926cc803284d01 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
@Caolan Any idea what LibreOffice does with they Interface Languages on initialization? I guess not, but I like to ask. And way (way) more off topic: would placing they xcd files into sqlite database have performance impact. Still loving to see sqlite being introduced for registrymodifications.xcu; that file is written insane amount of times; the benifit list: https://www.sqlite.org/aff_short.html didn't convince Miklos, yet
sberg knows far more about the config layer than I ever will, I'm unconvinced that sqlite would be a magic bullet
One aspect of having more localizations installed is that, yes, there are more .xcd files under share/registry/, and, yes, all of them are processed during start-up. But without actual profiling it is hard to tell whether that additional .xcd processing amounts to a relevant share of your reported start-up slowdown. (I tend to remember that I made measurements back in the days of the configmgr redesign introducing those .xcd files, and that they indicated rather insignificant slowdown, but I cannot remember any details.)
Created attachment 164792 [details] Screenshot VTune Profiler A slightly uninformative performance profile (non-debug/non-symbol build). I launched Writer with the V-Tune. There is a 4 second pause before the initialization really starts. V-Tune sadly shows no stack information for that period :-(
Hello Telesto, is this issue still reproducible with a master build ?
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