<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Idle LibreOffice consumes 100% CPU on i386" href="https://bugs.documentfoundation.org/show_bug.cgi?id=127344#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Idle LibreOffice consumes 100% CPU on i386" href="https://bugs.documentfoundation.org/show_bug.cgi?id=127344">bug 127344</a> from <a class="email" href="mailto:albrecht.dress@arcor.de" title="Albrecht Dreß <albrecht.dress@arcor.de>"> Albrecht Dreß</a> <pre>Created <a href="http://bugs.documentfoundation.org/attachment.cgi?id=160609" name="attach_160609" title="test LibreOffice 6.4.3 from Debian Buster backports on i386">attachment 160609</a> <a href="http://bugs.documentfoundation.org/attachment.cgi?id=160609&action=edit" title="test LibreOffice 6.4.3 from Debian Buster backports on i386">[details]</a> test LibreOffice 6.4.3 from Debian Buster backports on i386 I installed the latest packages, including the dbgsyms for core, writer and gtk3, from Debian buster backports on a Virtualbox 32 bit VM, running the latest buster with all updates (see file packages.log in the attached package). Then I cleared the user config, launched the writer from the XFCE menu, and waited ~10 minutes until the one cpu (out of 2) went to 100%. Then I opened gdb: | test@debian32:~$ rm -rf .config/libreoffice/ | [launch LO writer from the XFCE menu] | [wait until the cpu goes to 100%] | gdb /usr/lib/libreoffice/program/soffice.bin Htop reports a bunch of threads related to pid 1244, of which “soffice.bin” comsumes 100% cpu (see top.log). Running perf on pid 1244 results in the attached perf-report.log. In gdb, I attached to pid 1244, listed the threads, and a few times interrupted thread “soffice.bin” go get the bt (gdb.log). Please let me know if you need more information.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>