Description: Paint shows artifacts for <0,5 second) when zoom in/out on a table Steps to Reproduce: 1. Open the attached file 2. Scroll in/out using CTRL+SCROLL WHEEL. Notice a 'wave' from right to left in a split second.. Actual Results: Flashing (especially the top row) Expected Results: Smooth Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 93115d2c54d645bcf2f80fde325e3ede39dee4d5 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
Created attachment 175710 [details] Example file
Created attachment 175711 [details] Screencast
Created attachment 175712 [details] Still of frame of screencast
Also in Version: 7.1.0.0.alpha1+ (x64) Build ID: 94ea1c89e959069aa7c735317470712012df2362 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: nl-NL Calc: CL it present in (or simply not noticeable in) Version: 7.0.0.0.beta1+ (x64) Build ID: 2891e91a513520d68ea2b8c59c14335861a15253 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
I confirm it with Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL BTW: I think it's not worth to report it, until we have thousands of other open bugs.
Created attachment 175973 [details] Bibisect log Bisected to author Luboš Luňák <l.lunak@collabora.com> 2020-10-06 22:14:36 +0200 committer Luboš Luňák <l.lunak@collabora.com> 2020-10-08 13:40:14 +0200 commit d18731f71c60cbb6c02cabb042004b1aa9454de8 (patch) tree 36870456fc84f62b2ab85a3bad1971641856cbda parent 47fda617fc4dad8273919227ca45ea3b8b61aea1 (diff) track dirty areas for Skia drawing Updates to the screen in raster mode aren't _that_ slow, in fact it seems using SkRegion can make things slower because of manipulating the region, but with SkIRect this could sometimes help a bit. It also appears that StretchDIBits() that is used by the Windows raster code doesn't work correctly if only a subset of the y-axis range is specified, which reduces the usefulness. https://cgit.freedesktop.org/libreoffice/core/commit/?id=d18731f71c60cbb6c02cabb042004b1aa9454de8
(In reply to Dieter from comment #5) > BTW: I think it's not worth to report it, until we have thousands of other > open bugs. I still think it worth reporting (even with 1000 of other reports). In case more issues appear in the same area. Or simply the fact that a certain commit having a side-effect. Maybe more appear over time? And there might be some (minority) who find this problematic. People with epilepsy (flashing trigger an 'attack'), or idiots like me who find it distracting
Adding CC to Luboš Luňák
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
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://guestsarticles.com/