[Libreoffice-bugs] [Bug 112975] LibO is maxing out one core for a long time (since LibO 6.0)

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=112975

--- Comment #1 from Telesto <telesto at surfxs.nl> ---
Created attachment 136827
  --> https://bugs.documentfoundation.org/attachment.cgi?id=136827&action=edit
Bibisect log

Bibisect log attached

author  Jan-Marek Glogowski <glogow at fbihome.de> 2017-08-29 08:29:51 (GMT)
committer       Jan-Marek Glogowski <glogow at fbihome.de> 2017-09-26 11:53:28
(GMT)
commit  9679fb26558ea42e47ac9936cef329115a8fdf65 (patch)
tree    eee6c65d50667fc5b9924f98ce8f87a6df9d707a
parent  808d048694630303d895e818cfd5fb48c9d16738 (diff)
tdf#112288 Clarify Reschedule implementations
Application::Reschedule(true) must just process all currently
pending events and ignore all new events generated while processing
them. In contrast to Scheduler::ProcessEventsToIdle, this way it
can't busy-lock the application with background jobs.

This way we also can drop nMaxEvents from the Windows backend. This
limit was also never implemented on OSX and for the KDE4 backend
it's actually impossible to handle single events, and a call to
QAbstractEventDispatcher::processEvents works like this.

Also changes various call sites to just process all pending events
instead of some made up number of times.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20171007/e84ad0c9/attachment-0001.html>