Description: Dragging 3D fontwork or scroll past it or zoom in/out & in Writer is sluggish and a CPU hog Steps to Reproduce: 1. Open the attached file or insert Fontwork Favorite 9 or 11 Actual Results: Sluggish experience Expected Results: Same behavior as Draw Reproducible: Always User Profile Reset: No Additional Info: Version: 6.2.0.0.alpha1+ Build ID: 2e184378da6058af14acf208d6469fadf44d04ed CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2018-10-30_03:29:39 Locale: nl-NL (nl_NL); Calc: CL
Created attachment 146169 [details] Example file
Not in Version: 5.4.0.0.alpha0+ Build ID: aabc5aab5af27e929a81a6036d2f470ab1f5ac4d CPU Threads: 4; OS Version: Windows 6.29; UI Render: default; Layout Engine: new; Locale: nl-NL (nl_NL); Calc: CL Looks a lot like bug 120837 (most time spend in: Point::toPair)
I can't reproduce it in Version: 6.3.0.0.alpha0+ Build ID: cec7ae9f3c69ecc83462f28fc4987e37dc1b420e CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded is this issue still reproducible in master ?
Created attachment 148545 [details] Screencast LibO6.3 Repro Version: 6.3.0.0.alpha0+ Build ID: 6740443311268b7d918bf4f43134d64fb78a0109 CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-01-15_23:37:04 Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL
Created attachment 148546 [details] Screencast LibO6.3 zoom part
Dragging is responsive on Linux, but sluggish on Win. Zooming is a bit sluggish on Linux, but worse on Win. Arch Linux 64-bit Version: 6.4.0.0.alpha0+ Build ID: 1ce1c26dd98e6477139e08d1ebe89fa950ff5fb0 CPU threads: 8; OS: Linux 5.2; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 12 July 2019 Version: 6.4.0.0.alpha0+ (x64) Build ID: 25bf2c5c0074fbcc162c02593d896705e225b5b5 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-07-03_06:33:11 Locale: fi-FI (fi_FI); UI-Language: en-US Calc: threaded
Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug