Created attachment 115841 [details] rectangular hole artifacts in mirrored brush strokes SUMMARY Quick, high-thickness strokes appear to get rectangular "hole" artifacts erratically. I've exported to PNG to verify it's not just an editor view artifact. These holes appear in the PNG as well. I'm using a new laptop with 1060 maxq video card. Dell G7 16GB RAM. Windows 10 Home. I've updated NVidia drivers. I've tried turning OpenGL off, and a few different options in that same view... but not all of them. STEPS TO REPRODUCE 1. new document 3508x2480 2. select a basic-5-size brush 3. Make numerous strokes of varying width, usually quickly, using varying pressure on tablet OBSERVED RESULT The painted line will draw correctly, as will the mirror preview on the left - however after releasing the stylus, the line may exhibit rectangular "hole" artifacts. I've verified that this happens regardless of which side of the mirror I make my marks on. EXPECTED RESULT I would expect to not be missing rectangular chunks of the mirrored marks SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Krita Version: 4.1.5 Qt Version (compiled): 5.9.3 Version (loaded): 5.9.3 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.17134 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 OpenGL Info **OpenGL not initialized**
I'm sorry, but I haven't been able to reproduce this yet. I've seen similar reports, though. Can you reproduce it consistently? And if so, could you try the latest nightly build and see whether it's still reproducible? That has a completely different memory manager. See https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/
I was able to reproduce consistently. However, I tried the most recent nightly build - and this build doesn't appear to exhibit the problematic behavior. All mirrored marks behave as expected, with brushes of varying widths. https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/347/ Let me know if there is anything else I should try. Thanks!
No, that's sufficient, thanks. We probably won't release another 4.1, 4.2 will be the next release and that then has this bug fixed.
If this is fixed in 4.2, we should probably mark it as fixed for now. :)