Description: newest release of LO + LT (6.1.1). finally installs and works again ... but: opening a simple 5 pages document takes now 2 mins (instead of few secs under LO7.5 + LT5.9), i killed a 120 page document after 15 mins (CPU occupied to 50%) Steps to Reproduce: 0. LO 7.6 with new userprofile 1. have LT 6.1.1, background check disabled 2. open a medium document 3. wait ... Actual Results: takes ages to open Expected Results: should not take longer than 7.5 Reproducible: Always User Profile Reset: Yes Additional Info: with LT uninstalled, document open decently, not fast, but ok. Version: 7.6.0.1 (X86_64) / LibreOffice Community Build ID: 776eaf34564cbf3f034a0ba1fd1d5c32ff9ccf1c CPU threads: 4; OS: Linux 6.3; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
I could not reproduce with 5 pages of dummy text with LT extension 6.1.1 and: Version: 7.6.0.1 (X86_64) / LibreOffice Community Build ID: 776eaf34564cbf3f034a0ba1fd1d5c32ff9ccf1c CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Can you please provide an example document?
i did many experiments and tested various combinations. i could not install LT6.1.1 under LO7.5 (some java/api problems), and on the other hand, LT5.9.1 installed under LO7.6 does not work, i had to find a way to test crosswise. the only combination working: installing LT5.9.1 under LO7.5 and then upgrade to LO7.6 and miraculously LT5.9.1 is usable under LO7.6 AND works fine. no performance problems. so, i'm concluding: it's a LT6.1.1 problem. => my question: how to reassign this bug to LT?
(the status "new" generally is for someone independently confirming the issue, setting back to "unconfirmed") For issues that come from LT's side, please report them on their GitHub repository. But first, search through the existing reports to see if the issue is already tracked: https://github.com/languagetool-org/languagetool/issues?q=is%3Aissue+is%3Aopen+libreoffice If you find the corresponding issue, or report a new one, please link it here. Thank you!