<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - LanguageTool extension maxes out CPU with a long document" href="https://bugs.documentfoundation.org/show_bug.cgi?id=115757#c37">Comment # 37</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - LanguageTool extension maxes out CPU with a long document" href="https://bugs.documentfoundation.org/show_bug.cgi?id=115757">bug 115757</a> from <a class="email" href="mailto:todventtu@suomi24.fi" title="Buovjaga <todventtu@suomi24.fi>"> Buovjaga</a> <pre>(In reply to Noel Grandin from <a href="show_bug.cgi?id=115757#c36">comment #36</a>) > @Julien perf is not much use at looking inside java code. All we can tell is > that the CPU time is inside the GrammarChecking java code. (i.e. inside > LanguageTool) > > Tools like VisualVM or the Netbeans Profiler can look inside Java code, and > is probably what is necessary here. > > But at this point, it is no longer a bug in LibreOffice, so you are perhaps > better off logging this upstream at > <a href="https://github.com/languagetool-org/languagetool/issues">https://github.com/languagetool-org/languagetool/issues</a> I already created an issue last year: <a href="https://github.com/languagetool-org/languagetool/issues/1217">https://github.com/languagetool-org/languagetool/issues/1217</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>