<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Post-3.7.x memory leak, Radeon Evergreen, bisected"
href="https://bugs.freedesktop.org/show_bug.cgi?id=60028#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Post-3.7.x memory leak, Radeon Evergreen, bisected"
href="https://bugs.freedesktop.org/show_bug.cgi?id=60028">bug 60028</a>
from <span class="vcard"><a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=60028#c8">comment #8</a>)
<span class="quote">> Would it be good for me to bisect Mesa?</span >
If Mesa commit 6532eb17baff6e61b427f29e076883f8941ae664 (where code depending
on DRM minor 26 was first introduced) doesn't leak, yes please.
BTW, does setting the environment variable R600_HYPERZ=0 for the leaking
process(es) work around the problem?
<span class="quote">> The testing I have done so far was assuming the problem was in the kernel,
> [...]</span >
The fact that the memory is reclaimed on process exit makes that unlikely.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>