Description: There is a small unresponsiveness (1-2 sec) if I start typing. It's only happening the first time after launch. In the same timespan louno.ini is read for around 1100 times. It seems a bit excessive (and the cause of the lag). The same behavior doesn't exist in 4.4.6.3 Steps to Reproduce: 1. Launch Writer 2. Launch Process Monitor with the filter set to soffice.bin (and capture active) 3. Start typing something Actual Results: louno.ini is read for more than 1100 times in 2 seconds Expected Results: It doesn't seem right to me. I'm noticing two different request (osl_setFileTime & osl_getDirectoryItem) Part of the stack for osl_getDirectoryItem (copied from Process Monitor) sal3.dll osl_getDirectoryItem + 0x227 sal3.dll rtl_bootstrap_args_open + 0x6d sal3.dll rtl_reallocateMemory + 0x479a sal3.dll rtl_reallocateMemory + 0x62dd sal3.dll rtl_reallocateMemory + 0x4b0e sal3.dll rtl_reallocateMemory + 0x4f6d sal3.dll rtl_reallocateMemory + 0x59ff sal3.dll rtl_reallocateMemory + 0x5cfd sal3.dll rtl_reallocateMemory + 0x49b3 sal3.dll rtl_bootstrap_expandMacros_from_handle + 0x20 cppuhelper3MSC.dll cppu::OMultiTypeInterfaceContainerHelperInt32::removeInterface + 0xae8 cppuhelper3MSC.dll cppu::OMultiTypeInterfaceContainerHelperInt32::removeInterface + 0xa86 stocserviceslo.dll com_sun_star_comp_uri_UriReferenceFactory_get_implementation + 0x5a3 mergedlo.dll comphelper::getExpandedUri + 0xb9 mergedlo.dll SvtLinguConfig::SetProperty + 0xa71 mergedlo.dll SvtLinguConfig::GetDictionaryEntry + 0x40e mergedlo.dll SvtLinguConfig::GetActiveDictionariesByFormat + 0x186 spelllo.dll spell_component_getFactory + 0x8c64 mergedlo.dll lng_component_getFactory + 0x4eff mergedlo.dll lng_component_getFactory + 0xbb0a mergedlo.dll lng_component_getFactory + 0x87b5 mergedlo.dll lng_component_getFactory + 0x2581 mergedlo.dll lng_component_getFactory + 0x5e80 cppuhelper3MSC.dll cppu::createFactoryProxy + 0x4bb cppuhelper3MSC.dll cppu::createFactoryProxy + 0xd4c cppuhelper3MSC.dll cppu::createFactoryProxy + 0xc8e cppuhelper3MSC.dll cppu::OPropertySetHelper::setPropertyValues + 0xd0fc cppuhelper3MSC.dll cppu::OPropertySetHelper::setPropertyValues + 0xd6da Reproducible: Always User Profile Reset: No Additional Info: Found in Versie: 5.4.0.0.beta2 Build ID: 3cc1cdd8ee50f144e5514da51800a08119754d8f CPU-threads: 4; Besturingssysteem:Windows 6.2; UI-render: standaard; Locale: nl-NL (nl_NL); Calc: CL User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
This is definitely related to spell checker initialization, as it doesn't occur if automatic spell checking is turned off. Reproduced with 3.5.0.3, but I assume it's inherited.
Quote from https://gerrit.libreoffice.org/#/c/56095/ Tor Lillqvist; Patch Set 6: The Right Way to fix the problem would of course be to re-work the code path that is taking so long; why does the code insist on initialising (in some sense) stuff for languages not even used at the moment? Adding debugging printout in various places one sees that LngSvcMgr::getAvailableServices() is called for all potential language/locale combinations. Why? And org.libreoffice.comp.pyuno.Lightproof.pt_BR, org.libreoffice.comp.pyuno.Lightproof.ru_RU, etc even if no document with text in Brazi.ian Portuguese or Rssian os nowhere open. Etc. My God, it's full of crap.
With [1] this probably shifted to startup, and I would also assume the number of queries haven't changed. [1] https://cgit.freedesktop.org/libreoffice/core/commit/?id=f1d9aca4bf596c0a3be44483b1d60867f12683ec
Dear Telesto, 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
Dear Telesto, 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 https://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
Dear Telesto, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug