<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Crash happens when drawArrays after calling continuously glTexImage3D many times" href="https://bugs.freedesktop.org/show_bug.cgi?id=111083#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Crash happens when drawArrays after calling continuously glTexImage3D many times" href="https://bugs.freedesktop.org/show_bug.cgi?id=111083">bug 111083</a> from <a class="email" href="mailto:kenneth@whitecape.org" title="Kenneth Graunke <kenneth@whitecape.org>"> Kenneth Graunke</a> <pre>(In reply to xinghua from <a href="show_bug.cgi?id=111083#c9">comment #9</a>) > Does It mean that 19.0.x is not very stable? I think this bug is very > critical, many paths could run to crash situation. One issue in a pathological test case is hardly an indicator of driver quality. Backporting bug fixes for unit tests isn't critical - fixing bugs hit by actual end user applications is critical. Unless there's some real application running into trouble here, I wouldn't bother making an extra point release for an EOL'd release series. We had this bug for probably 10 years and nobody noticed until this new unit test suite came along, so I'm not really convinced that it's critical. ChromeOS also usually tracks master (and certainly wouldn't be staying on an old 19.0.x release), so it shouldn't matter much for them.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>