<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [r600g] Memory leak with celestia, RV790"
href="https://bugs.freedesktop.org/show_bug.cgi?id=75732#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [r600g] Memory leak with celestia, RV790"
href="https://bugs.freedesktop.org/show_bug.cgi?id=75732">bug 75732</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=75732#c4">comment #4</a>)
<span class="quote">> [...] since valgrinding 32 bit WoW on a 64 bit box is currently beyond me,</span >
As suggested in your WoW bug report, please try valgrind on replaying an
apitrace instead.
<span class="quote">> I am hunting for memory errors in other workloads instead, in the hope that
> they might provide some insight.)</span >
valgrind finds one 352 byte leak with celestia. That can't possibly explain the
issues you're having with WoW.</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>