<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - swr driver leaks memory (texture management)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101467#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - swr driver leaks memory (texture management)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101467">bug 101467</a>
from <span class="vcard"><a class="email" href="mailto:bruce.cherniak@intel.com" title="Bruce Cherniak <bruce.cherniak@intel.com>"> <span class="fn">Bruce Cherniak</span></a>
</span></b>
<pre>Well, technically the swr driver isn't "leaking" memory, it's just deferring
deletion of the underlying storage until a sync point.
Because the loop is simply:
for (bigly_number_of_textures) {
allocate_texture()
draw_something()
delete_texture()
}
read_pixels()
There is nothing forcing synchronization until the read_pixels. So, at the end
of the loop, there are 5000 free() queued up, that all get flushed on the
read_pixels. This accounts for ~20GB of allocated system memory.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>