<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Image compositor can pass invalid coordinates to pixman_fill()" href="https://bugs.freedesktop.org/show_bug.cgi?id=90120#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Image compositor can pass invalid coordinates to pixman_fill()" href="https://bugs.freedesktop.org/show_bug.cgi?id=90120">bug 90120</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>Created <a href="attachment.cgi?id=115240" name="attach_115240" title="Preliminary stroke validation">attachment 115240</a> <a href="attachment.cgi?id=115240&action=edit" title="Preliminary stroke validation">[details]</a> <a href='page.cgi?id=splinter.html&bug=90120&attachment=115240'>[review]</a> Preliminary stroke validation Imo, the important thing here, if we take the input validation path, is to only apply it at the boundary of the fixed point representation i.e. so that we only reject extreme values when rastering, but pass through to vector backends (or apply their own range checking). However, extreme line_width has a very simple interpretation and I think it would be better for cairo to have a slow-but-safe rasteriser. Detecting when the input path and style will produce illegal fixed point values and switching to a double representation will allow us to generate output without crashing with a slight loss of precision.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>