<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - EDITING. 100% CPU usage after a few minutes with certain documents."
href="https://bugs.documentfoundation.org/show_bug.cgi?id=118991#c23">Comment # 23</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - EDITING. 100% CPU usage after a few minutes with certain documents."
href="https://bugs.documentfoundation.org/show_bug.cgi?id=118991">bug 118991</a>
from <span class="vcard"><a class="email" href="mailto:ross.stormcrow@gmail.com" title="ross.stormcrow@gmail.com">ross.stormcrow@gmail.com</a>
</span></b>
<pre>This is an example file showing the 100% CPU utilization bug. This will
completely hang 6.0.x on Ubuntu for several minutes before it eventually
displays. Converting it using lowriter --convert-to to an ODT then opening it
in an interactive session will hang 6.0.x indefinitely on a SandyBridge era
Intel Core i5 2400S CPU. Converting the same file to a PDF then viewing it
takes a trivial amount of time (using lowriter --convert-to takes seconds to
convert then display in a PDF viewer). On a Dell laptop with an i5 8300H on
Windows 10 with LO 6.2.3.2 AMD64 it still takes several minutes to display with
the CPU pegged to 100%, but it will eventually do so and you can close it
without hanging LO.</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>