https://bugs.kde.org/show_bug.cgi?id=492529
William Bader <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Ever confirmed|0 |1 Resolution|NOT A BUG |--- --- Comment #11 from William Bader <[email protected]> --- While looking at another issue in poppler, I found the bug that caused the slowness. When a Splash is created without antialiasing, there is no aaBuf, so Splash::shadedFill() fails and Gfx falls back to filling the axial, radial or function shading as many small paths. This PDF contains 43 axial (type 2) and 144 radial (type 3) shadings. Those are exactly the ones that hit the fallback path. With vector antialiasing off on master, the Splash has no aaBuf, so Splash::shadedFill() fails. Gfx then paints each of the 187 shadings as many small filled paths, and that takes the time. With antialiasing on, the shading goes through shadedFill() and is nearly instant. That's why turning antialiasing on in Okular made it about 50 times faster instead of a few times slower. See the merge request at https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/2411 -- You are receiving this mail because: You are watching all bug changes.
