Announcement: LanguageTool 2.9

Kumara · May 6, 2015, 10:57pm

manomi [via LanguageTool User Forum] wrote thus at 08:44 AM 06-05-15:

Very recently, I have updated LibreOffice to 4.4.3.2 and no longer
receives that error, with LT 2.9 installed, when opening the file in
question… I will continue using LibreOffice 4.4.3.2 and LT 2.9,
and if there is a problem, I will report it here.

I suppose it remains ok, until the memory usage hits the java roof.

chr_hoe · May 7, 2015, 10:35am

I played a bit with this -Xmx parameter as I couldn’t imagine that it doesn’t work at all and it turned out that there is a certain limit up to which this parameter works OK and above which LO throws this “JRE defect” error.
For my system this limit is at -Xmx717M which still works or -Xmx718M which causes the error. I reinstalled your first testing version to check which influence that has on the memory figures and found weird behaviour:

with increased memory many times the “About” dialog doesn’t show up at all. That seems to get worse with higher memory figures in -Xmx parameter. Every time I tried to open the About dialog and it didn’t show up I get an “osl::create failed” error on LO exit.
the “osl::create failed” still happens with this LT version - the increased memory doesn’t help (with an empty document the figures are “Java max/total/free memory: 494MB, 15MB, 10MB” with -Xmx511M)
it seems to make a difference how a document is loaded - best case is opening Writer first and loading the questionable document from Writer. Worst case is launching Writer by double clicking on the document in the explorer. Why? I don’t know!

All in all it seems to me that memory is a problem here but not the only one. For example an interesting question is why the necessary amount of memory for one and the same document can be so different depending on the way it is loaded. One time the About dialog showed up it gave something like 494MB, 246MB, 63MB for test_doc_1 after loading it from explorer and now it is 494MB, 33MB, 6MB after loading the same document from the LO open dialog. Big difference! Looks like we have to think a bit beyond lack of memory…

And regarding LO version - I’m using 4.4.3.2 now, too and it doesn’t make any difference to me.

Best regards,
Christian

dnaber · May 7, 2015, 11:15am

You can ignore the second and the third value in the about dialog, it’s normal that they change a lot over time. Can you provide documents that can be used to reproduce the problem?

dnaber · May 8, 2015, 9:07am

Could you try if “-Xmx718M” works on the command line? If it does, this really seems to be a bug in LO and should be reported.

chr_hoe · May 8, 2015, 11:44am

Baby_Talk_am_Beispiel_des_Polnischen-chr-ori.odt (556 KB)

This is one of the documents I use for testing. I normally use the navigator to jump a bit back and forth in the document. Most of the time this is already sufficient to crash LO - if not I jump to “Literaturverzeichnis” and start marking the book titles with the appropriate language (Polish or English) jumping to a random chapter after each marking and back to the “Literaturverzeichnis” - I rarely can mark more than on book title before LO crashes.

Regarding the java option “-Xmx718M” - yes, I tried and it worked on the command line. But as I’m always nosey I started trying if there is an upper limit for the reserved memory on the command line as well - and as expected there is one … but surprisingly it is exactly twice the limit within LO: with “-Xmx1434M” java still starts, with any value above it crashs. Can this be just by coincidence? I don’t think so! I didn’t got the logic up to now but I don’t believe this just by chance!

dnaber · May 8, 2015, 12:08pm

Thanks for the document, I will later test with that. About the limit: 1,4GB is reasonable, see Maximum Java heap size of a 32-bit JVM on a 64-bit OS - Stack Overflow - why LO offers only half of that, I don’t know.

dnaber · May 9, 2015, 7:56pm

I cannot reproduce the problem with this document, neither with LO 4.3 nor with 4.4, not even when I limit the memory to -Xmx256M. But the test was under Linux, maybe I can get a virtual machine to try it under Windows.

For German, I have made some memory optimizations that are now in the very latest snapshot. It would be nice if you could try if that helps: https://languagetool.org/download/snapshots/LanguageTool-20150509-snapshot.oxt

dnaber · May 11, 2015, 7:52pm

We’ve made another change and there’s a first report that it helps. If the 20150509 snapshot doesn’t help, please try this:

https://languagetool.org/download/snapshots/LanguageTool-20150511-snapshot.oxt

chr_hoe · May 11, 2015, 9:51pm

Dnabber, I’m sorry but I’m abroad this week and not sure if I will have
time for testing. Will have a close look next week.

Am 11. Mai 2015 21:09:20 schrieb “dnaber [via LanguageTool User Forum]”
ml-node+s2306527n4642731h35@n4.nabble.com:

We’ve made another change and there’s a first report that it helps. If the
20150509 snapshot doesn’t help, please try this:

https://languagetool.org/download/snapshots/LanguageTool-20150511-snapshot.oxt

If you reply to this email, your message will be added to the discussion below:
http://languagetool-user-forum.2306527.n4.nabble.com/Announcement-LanguageTool-2-9-tp4642477p4642731.html

To unsubscribe from Announcement: LanguageTool 2.9, visit
http://languagetool-user-forum.2306527.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4642477&code=Y2hyaXN0aWFuQGhvZXJsbGUuZGV8NDY0MjQ3N3wtMTc5NDA2Nzk0NQ==

Kumara · May 12, 2015, 4:49am

dnaber [via LanguageTool User Forum] wrote thus at 03:52 AM 12-05-15:

We’ve made another change and there’s a first report that it helps.
If the 20150509 snapshot doesn’t help, please try this:
https://languagetool.org/download/snapshots/LanguageTool-20150511-snapshot.oxt https://languagetool.org/download/snapshots/LanguageTool-20150511-snapshot.oxt

If you can wait, I’ll be able to do this on Thursday.

dnaber · May 14, 2015, 8:02pm

We have two users on the mailing list who confirmed the issue has been fixed. So we’ve released 2.9.1:
http://languagetool-user-forum.2306527.n4.nabble.com/Announcement-LanguageTool-2-9-1-td4642764.html

chr_hoe · May 14, 2015, 10:33pm

Dear Daniel, I will be back on Saturday and try the new version on Monday
at latest. I’ll give you my feedback asap.

Best regards, Christian

Am 14. Mai 2015 21:19:39 schrieb “dnaber [via LanguageTool User Forum]”
ml-node+s2306527n4642765h89@n4.nabble.com:

We have two users on the mailing list who confirmed the issue has been fixed.
So we’ve released 2.9.1:
http://languagetool-user-forum.2306527.n4.nabble.com/Announcement-LanguageTool-2-9-1-td4642764.html

If you reply to this email, your message will be added to the discussion below:
http://languagetool-user-forum.2306527.n4.nabble.com/Announcement-LanguageTool-2-9-tp4642477p4642765.html

To unsubscribe from Announcement: LanguageTool 2.9, visit
http://languagetool-user-forum.2306527.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4642477&code=Y2hyaXN0aWFuQGhvZXJsbGUuZGV8NDY0MjQ3N3wtMTc5NDA2Nzk0NQ==

Kumara · May 15, 2015, 10:13am

dnaber [via LanguageTool User Forum] wrote thus at 03:52 AM 12-05-15:

We’ve made another change and there’s a first report that it helps.
If the 20150509 snapshot doesn’t help, please try this:
https://languagetool.org/download/snapshots/LanguageTool-20150511-snapshot.oxt https://languagetool.org/download/snapshots/LanguageTool-20150511-snapshot.oxt

I’ve used 20150511-snapshot since this morning. So far no
freezing/crashing. “Save as” can be done. LT flags errors as usual.
The bug is probably fixed.

chr_hoe · May 19, 2015, 8:33am

Yesterday I’ve installed LT 2.9.1 release version I tried all my test documents without “success” - or better to say with success: no crashes any more!

Good work Daniel - you’ve finally got it! It wasn’t just a memory problem, wasn’t it?