https://bugs.documentfoundation.org/show_bug.cgi?id=163945
Patrick (volunteer) <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |bibisectRequest --- Comment #39 from Patrick (volunteer) <[email protected]> --- (In reply to Seb from comment #33) > I have some new information, but the various issues are getting a bit mixed > up so let me clarify what I see on my machine. All of this is with > skia/metal except where stated. > Thank you for your detailed analysis. I cannot reproduce most of what is in your list but sometimes I see the "no tooltip appears" when resizing a Calc column via dragging. I can try reverting any recent Skia changes in my local build and see if I can make that specific bug disappear. If that doesn't uncover any specific change, we may need someone who can reproduce most of the bugs to do a bibisect to find which change caused this. I know that a newer version of Google's Skia code was recently put in master but we would need a bibisect to find the change: https://wiki.documentfoundation.org/QA/Bibisect (In reply to Seb from comment #33) > Also want to say I am a developer (on other platforms) so if it would be > very helpful for me to run profiling or try out speculative changes before > they hit master then I could get set up to do that. That is very good to hear. If you Xcode installed, you should be able to connect Xcode's Instruments application or lldb to a running nightly build. No need to install any third party packages. It won't work for release builds but for a nightly or local build, debugging and profiling are enabled by default. Here are the steps I use: 1. Launch a nightly or local build and get the application in the state you want to test (e.g. open an empty Calc document and set the selected cell) 2. In a Terminal application window, run the following command: open /Applications/Xcode.app/Contents/Applications/Instruments.app 3. In Instruments, select "Time Profiler" and in the window that appears, select "soffice" to connect to LibreOffice and press the red Start icon 4. Do your testing in LibreOffice (e.g. change a column width rapidly) 5. In Instruments, press the Stop icon If you are interested in doing a local build, you could try out possible fixes without having to go through the "commit and wait for the next nightly build" process. That might be useful for joint debugging as well. I use LibreOffice's LODE environment to build LibreOffice. The thing I really like about LODE is that it downloads all of the third party packages automatically and puts them in a LODE folder so it doesn't pollute your existing macOS configuration. With LODE, you only need to install Xcode and a Java Development Kit (JDK): https://wiki.documentfoundation.org/Development/lode -- You are receiving this mail because: You are the assignee for the bug.
