<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - High CPU load when scrolling a document with many comments"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=61558#c51">Comment # 51</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - High CPU load when scrolling a document with many comments"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=61558">bug 61558</a>
from <span class="vcard"><a class="email" href="mailto:noelgrandin@gmail.com" title="Noel Grandin <noelgrandin@gmail.com>"> <span class="fn">Noel Grandin</span></a>
</span></b>
<pre>Some notes from my unsucessful attempt to fix this:
(1) I can fix the typing part by removing the WB_DIALOGCONTROL flag from the
SwEditWin constructor. The time is being spent searching through tons of child
windows on every key stroke. I don't think this flag is necessary because we're
not doing dialog things in the main window.
But I'm probably wrong and there is some weird reason we need it.
(2) I can fix the paging/scrolling part by commenting out the
if ( pPostItMgr ) // #i88070#
{
pPostItMgr->Rescale();
pPostItMgr->CalcRects();
pPostItMgr->LayoutPostIts();
}
code in void SwViewShell::VisPortChgd
As far as I can tell, the UI still works fine without those lines of code,
because don't actually need to run the bulk of layout when the viewport
changes.
According to the bug report in the comment
<a href="https://bz.apache.org/ooo/show_bug.cgi?id=88070">https://bz.apache.org/ooo/show_bug.cgi?id=88070</a>
they are there because accessibility stuff is being calculated during the
layout loop. So one possible fix would be to pass some sort of flag down to
CalcRects and LayoutPostIts to say "only do the accessibility stuff"</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>