<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Extension Manager freezes after installing oxt on Mac LibreOffice version 6.1.4.2" href="https://bugs.documentfoundation.org/show_bug.cgi?id=122749#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Extension Manager freezes after installing oxt on Mac LibreOffice version 6.1.4.2" href="https://bugs.documentfoundation.org/show_bug.cgi?id=122749">bug 122749</a> from <a class="email" href="mailto:michael.meeks@collabora.com" title="Michael Meeks <michael.meeks@collabora.com>"> Michael Meeks</a> <pre>Trace (thanks Alex) looks rather like the other problem we have when building with a modern compiler for OSX. I would rather suspect that we are doing a ton of rendering - at high frequency - and that OSX is batching all of this up to be rendered later. Then - when it comes to render it - it tries to do clever scene analytics to partition the work (which makes sense) - but their apparently recursive algorithm blows up for large amounts of data and hangs. May be compounded by some producer/consumer mismatch I guess - such that one thread is queueing new things to render regularly while the other is fighting a loosing battle to partition / analyse that for GPU dispatch somewhere else. At least, that's my guess. Might be interesting to see what VCL rendering APIs are being called - and/or how much 'paint' stuff is actually going on - possibly a SAL_LOG=1 output for a dbgutil build would show that. Thanks !</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>