<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - System hang when use glTexImage3D to specify a 3D texture image" href="https://bugs.freedesktop.org/show_bug.cgi?id=104760#c27">Comment # 27</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - System hang when use glTexImage3D to specify a 3D texture image" href="https://bugs.freedesktop.org/show_bug.cgi?id=104760">bug 104760</a> from <a class="email" href="mailto:lionel.g.landwerlin@linux.intel.com" title="Lionel Landwerlin <lionel.g.landwerlin@linux.intel.com>"> Lionel Landwerlin</a> <pre>(In reply to Mark Janes from <a href="show_bug.cgi?id=104760#c26">comment #26</a>) > Is the correct resolution to track graphics memory in a way that allows the > OOM killer to target the process that is locking up the system? > > Lionel's workaround will handle this particular case, but there are many > other ways to produce the same effect. Indeed a sim(In reply to Denis from <a href="show_bug.cgi?id=104760#c24">comment #24</a>) > But according to Danylo, there are two issues here, in mesa side and in > kernel side. > So possibly we need one ticket in i965 and one (current) in drm/intel? > Just in case if issue will be fixed only in one place... I don't think a simple ioctl with the i915 driver with a particular size should lock up the system. Any userspace program can do that, this isn't related to Mesa.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>