<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Webgl Pointclouds flickers" href="https://bugs.freedesktop.org/show_bug.cgi?id=105224#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Webgl Pointclouds flickers" href="https://bugs.freedesktop.org/show_bug.cgi?id=105224">bug 105224</a> from <a class="email" href="mailto:itoral@igalia.com" title="Iago Toral <itoral@igalia.com>"> Iago Toral</a> <pre>I was surprised that this was never caught by Jenkins before, because in theory, it should affect all situations that involve point sprite functionality and we have tests for that in Piglit. I did some investigation and it turns out that the tests are passing because the point sprite varying is the only input to the FS in these tests and the hardware has a requirement by which our URB must have at least one entry, so we were padding the URB size to have exactly one offset. This means that when we took the number of inputs from the URB size alone we would count 2, the minimum we can have (each URB offset packs 2 slots), and since the test only required one, it would work. I'll try to add another test to piglit that adds some user varyings so we can replicate the problem and add regression testing for it.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>