[Bug 93720] Random crashes on (EE) TouchListenerGone: couldn't allocate events
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Jan 25 07:40:34 PST 2016
https://bugs.freedesktop.org/show_bug.cgi?id=93720
--- Comment #6 from Chris Wilson <chris at chris-wilson.co.uk> ---
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 <chris at chris-wilson.co.uk>
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 <franck.delache at grassvalley.com>
References: https://bugs.freedesktop.org/show_bug.cgi?id=93720
Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
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?
--
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160125/51fa850c/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list