<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Random crashes on (EE) TouchListenerGone: couldn't allocate events" href="https://bugs.freedesktop.org/show_bug.cgi?id=93720#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Random crashes on (EE) TouchListenerGone: couldn't allocate events" href="https://bugs.freedesktop.org/show_bug.cgi?id=93720">bug 93720</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>Hmm, a damage allocation failed and subsequent NULL dereference. Looks like it was marked as "all-damaged" so it would have worked fairly normally - just should have failed to do partial migrations. commit 21fa92a9ba254527a8661ddde837c7a4c5ff5493 Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Date: Mon Jan 25 15:37:01 2016 +0000 sna/damage: Prevent freeing a NULL damage marked as all-damage After an allocation failure, we may mark a NULL damage pointer as being all-damaged. This works on the whole as most places we only ask whether it is all or not damaged, and if we do a partial fallback we should just then migrate the whole pixmap. However, we tried to destroy the NULL damage pointer, and crashed. Reported-by: Franck Delache <<a href="mailto:franck.delache@grassvalley.com">franck.delache@grassvalley.com</a>> References: <a class="bz_bug_link bz_status_NEW " title="NEW - Random crashes on (EE) TouchListenerGone: couldn't allocate events" href="show_bug.cgi?id=93720">https://bugs.freedesktop.org/show_bug.cgi?id=93720</a> Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> That should prevent this specific crash. So given the exorbitant number of objects for Xorg - we definitely have a leak somewhere along the driver stack. Next question, what does xrestop report after a high uptime?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>