<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:albrecht.dress@arcor.de" title="Albrecht Dreß <albrecht.dress@arcor.de>"> <span class="fn">Albrecht Dreß</span></a>
</span> changed
<a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Idle LibreOffice consumes 100% CPU on i386"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=127344">bug 127344</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEEDINFO
</td>
<td>UNCONFIRMED
</td>
</tr>
<tr>
<td style="text-align:right;">Ever confirmed</td>
<td>1
</td>
<td>
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Idle LibreOffice consumes 100% CPU on i386"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=127344#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Idle LibreOffice consumes 100% CPU on i386"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=127344">bug 127344</a>
from <span class="vcard"><a class="email" href="mailto:albrecht.dress@arcor.de" title="Albrecht Dreß <albrecht.dress@arcor.de>"> <span class="fn">Albrecht Dreß</span></a>
</span></b>
<pre>Thanks a lot for your feedback!
The short answer: the bug is still present in safe mode.
Long answer:
* installed Debian Buster/32 Bit from scratch on a newly created VirtualBox
6.0.12 VM
* installed all Debian updates, and the VBox guest additions
* removed all libreoffice deb's installed during the Buster install
* downloaded the packages LibreOffice_6.2.7_Linux_x86_deb.tar.gz and
LibreOffice_6.2.7_Linux_x86_deb_langpack_de.tar.gz (just to be sure, if
i18n/l10n makes any difference), and installed all deb's from both
* launched libreoffice6.2 from a terminal
* selected from the menu (German Locale) “Hilfe -> Im abgesicherten Modus neu
starten…” and from the dialogue “Im abgesicherten Modus fortfahren” (= “safe
mode”)
* opened a new Writer document; window title says “[…] abgesicherter Modus”
* leave Writer idle for ~35 minutes: soffice.bin goes to 100% CPU in top
Note 1: compared to the earlier tests in normal mode, it took longer for the
issue to pop up in safe mode. As this is just a single test, I don't know if
this is of any significance, though.
Note 2: on the MacBookPro5,5 (which is my wife's “production” machine, so I
could not run the safe mode test there yet), the effect occurred on a freshly
installed system, i.e. with a default profile.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>