<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Xorg memory leak with >=xf86-video-intel-2.99.901 and above"
href="https://bugs.freedesktop.org/show_bug.cgi?id=70924#c79">Comment # 79</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Xorg memory leak with >=xf86-video-intel-2.99.901 and above"
href="https://bugs.freedesktop.org/show_bug.cgi?id=70924">bug 70924</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>This should prevent it from taking the recursive path in the first place:
commit dc61705a6e425952de4c81c2320382af07cf948a
Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Date: Tue Nov 5 08:49:28 2013 +0000
sna: Use an inplace exchange for large untiled BO
On older architectures, large BO have to be untiled and so we can reuse
an existing CPU bo by adjusting its caching mode.
References: <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Xorg memory leak with >=xf86-video-intel-2.99.901 and above"
href="show_bug.cgi?id=70924">https://bugs.freedesktop.org/show_bug.cgi?id=70924</a>
Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
and this should fix the recursion:
commit f3225fcb38686f3b9701725bf3a11ecf1c100c3f
Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Date: Tue Nov 5 08:38:22 2013 +0000
sna: Be move conservative with tiling sizes for older fenced gen
The older generations have stricter requirements for alignment of fenced
GPU surfaces, so accommodate this by reducing our estimate available
space for the temporary tile.
Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>