https://bugs.kde.org/show_bug.cgi?id=453332
--- Comment #2 from Torsten Rahn <r...@kde.org> --- Hm, I haven't been able to trigger this when choosing "HighQuality" rendering during Animations (See Settings) - this uses void ScanlineTextureMapperContext::pixelValueApproxF instead of void ScanlineTextureMapperContext::pixelValueApprox. So I guess that this happens due to a rounding error which calculates the position to be outside the "last/first" tile in a column. Since nextTile() will still "stay" on the same tile we will reach out of bounds. The safe and lazy solution would be to correct the Y value to be still within the bounds. I wonder whether this issue could also be triggered for the x-case -- You are receiving this mail because: You are watching all bug changes.
