Description: For macOS, currently, LibreOffice is not built with XCode 10, release build bots have had to be switched back to XCode 9, as building with XCode 10 causes repeated overload in calls to CoreGraphics functions leading to an inevitable crash. The aim of this bug is just to bear in mind that this problem is unlikely to go away by itself and at some stage will need fixing. Steps to Reproduce: 1) Build LO source code with XCode 10 2) Start the resulting app from the build 3) Scroll anywhere in a menu with an up/down scrollbar or resize window then scroll, watch LO make repeat calls to CG functions causing it to eventually consume all resources and/or crash. Actual Results: See steps to reproduce Expected Results: Scrolling, window resizing, should behave normally and not cause excessive system resource consumption Reproducible: Always User Profile Reset: No Additional Info:
Note that this follows on from bug 121778
Confirmed by Tor in bug 121778 comment 76: "At least the resize-Calc-document, scroll-back-and-forth-a-bit scenario still causes the process to get stuck at 100% cpu usage in a master build with Xcode 10.1."
*** Bug 125145 has been marked as a duplicate of this bug. ***
Tomaž Vajngerl committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/959e8ae7ea33ce94dd80ee8ea172b6db64593873%5E%21 tdf#124271 use the bitmap context, handle scaling It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Testing with Version: 6.3.0.0.alpha1+ Build ID: 92b0b8d78d69bd917842b09af7888b402144baeb CPU threads: 4; OS: Mac OS X 10.14.4; UI render: default; VCL: osx; Locale: fr-FR (fr_FR.UTF-8); UI-Language: en-US Calc: threaded seems indeed to show that the problem no longer occurs, marking as resolved fixed, thanks !