https://bugs.documentfoundation.org/show_bug.cgi?id=104312
Michael Meeks <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #27 from Michael Meeks <[email protected]> ---
> Surely the correct way to handle this is to avoid making the entire interface
> freeze whilst the widgets are processed. Can't this be handled asynchronously?
I assume it is handled asynchronously - however, it is possible that that
happens with too high a priority; and/or that we may need to improve
prioritization of tasks to ensure that even if we hit 'idle' (ie. all tasks
done) - that we don't allow a low priority task that last-time took <N>
milliseconds to consume more than a certain budgeted time each second or so -
to somehow push these guys off so they don't block event processing =)
But of course - I could be wrong, and it could be handled synchronously; and -
as Caolan says, prolly the easiest fix is profiling to find out why it is quite
so slow. That's easy to do with a -non- dbgutil build, that has debugging
symbols and callgrind/cachegrind =)
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
