<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Edit with external tool causes a CPU hit"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=134157#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Edit with external tool causes a CPU hit"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=134157">bug 134157</a>
from <span class="vcard"><a class="email" href="mailto:michael.meeks@collabora.com" title="Michael Meeks <michael.meeks@collabora.com>"> <span class="fn">Michael Meeks</span></a>
</span></b>
<pre>Well - the idle work is fine - we do fast idles, when we are idle. Of course if
someone makes a busy loop using an idle handler that never completes - we hit
100% CPU. If they leak that busy idle handler then ... we get this effect.
I would go read the edit with external tool code, and work out why an idle
handler is used there, and/or turn it into a 250ms timeout or so.
HTH =)</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>