<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Segmentation fault when using a complex path for clip and stroke" href="https://bugs.freedesktop.org/show_bug.cgi?id=74779#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Segmentation fault when using a complex path for clip and stroke" href="https://bugs.freedesktop.org/show_bug.cgi?id=74779">bug 74779</a> from <a class="email" href="mailto:jlahd@iki.fi" title="Jussi Lahdenniemi <jlahd@iki.fi>"> Jussi Lahdenniemi</a> <pre>Had to get this working (at least to some extent), so I did a bit of research on the problem. The root cause seems to be that in certain circumstances the edges in the sweep list end up in a wrong order. When after that new edges are inserted they may end up at _very_ wrong positions, and before long the whole list is all messed up. Unfortunately, I did not have the time to find a real fix, but I worked around the problem by adding some NULL checks to the active_edges function (see the attached workaround patch), which at least makes the SIGSEGV disappear. The result is probably not pixel perfect, as the edges are still in the wrong order, but that's not that big an issue for me. I am also attaching another test case, reproduced from real live data this time, which demonstrates hopefully a little less pathological case for examination.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>