Description: for the second time, out off nowhere I get an errormessage. can't note any error or loose of functions or reason. Steps to Reproduce: 1.don't know 2. 3. Actual Results: Message: An error has occured in languageTool 4.5.1 (2019-03-28 10:47): java.lang.IndexOutBoundsException: Index: 2399, Size: 2399 Stacktrace: java.lang.IndexOutBoundsException: Index: 2399, Size: 2399 at java.util.ArrayList.rangeCheck(Unknown Source) at java.util.ArrayList.get(Unknown Source) at org.languagetool.openoffice.singleDocument.getParaPos(SingeDocument.java:380) at org.languagetool.openoffice.singleDocument.getCheckresults(SingleDucument.java:123) at org.languagetool.openoffice.MultiDocumentHandler.getCheckresults(MultiDucumentHandler.java:129) at org.languagetool.openoffice.main.doProofreading(Main.java:150) OS:Windows 7 an amd64, java version 1.8.0_211 from Oracle Corporation Expected Results: not show messages like this. don't know what's all about. Reproducible: Sometimes User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: de Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: yes
Without steps to reproduce this, it's difficult to investigate. Anyway, you may do this: - uninstall extensions - upgrade Libreoffice to 6.2.3 - rename your LO profile directory (see https://wiki.documentfoundation.org/UserProfile#Windows) - reinstall extensions If you still reproduce this, try to find steps to reproduce this. Let's put this bugtracker to NEEDINFO, waiting for your feedback.
I downloaded the sources of the extension. This line in src/main/java/org/languagetool/openoffice/SingleDocument.java may be buggy: 378 if (!chPara.equals(allParas.get(nParas))) { Indeed, some lines above, there's some bound checking: 348 if (nParas >= 0 && nParas < allParas.size() && chPara.equals(allParas.get(nParas))) { Let's put this one to NEW then. I created bugtracker upstream, see https://github.com/languagetool-org/languagetool/issues/1586
Just for information, the pb has been fixed upstream. I've just asked if the fix will be in the next release 4.6 planned end of June. See comments here: https://github.com/languagetool-org/languagetool/issues/1586
(In reply to Julien Nabet from comment #3) > Just for information, the pb has been fixed upstream. > I've just asked if the fix will be in the next release 4.6 planned end of > June. > See comments here: > https://github.com/languagetool-org/languagetool/issues/1586 These info have been confirmed. Let's put this one to NOTOURBUG since it's not due to LO but to an extension.