<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - ANV driver doesn't release memory"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107899#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - ANV driver doesn't release memory"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107899">bug 107899</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>The accumulation of i915_request implies there is a fence leak. Assuming it is
not internal (an unmatched dma_fence_get/dma_fence_put), all userspace owners
would be tied to an fd and eventually one would notice the fd exhaustion (after
a few million depending on rlimit). But for the fd to stick around requires the
process to be kept alive, which would imply the fence fd being passed to a
display server. I don't think that is how fences are handled under X, which
makes the likelihood of it being a singular userspace fence leak less likely.
'ls -1 /proc/$suspect/fd/ | wc -l' might be interesting to watch.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>