<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:nhaehnle@gmail.com" title="Nicolai Hähnle <nhaehnle@gmail.com>"> <span class="fn">Nicolai Hähnle</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - XCOM: Enemy Unknown Causes lockup"
href="https://bugs.freedesktop.org/show_bug.cgi?id=80419">bug 80419</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>nhaehnle@gmail.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - XCOM: Enemy Unknown Causes lockup"
href="https://bugs.freedesktop.org/show_bug.cgi?id=80419#c93">Comment # 93</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - XCOM: Enemy Unknown Causes lockup"
href="https://bugs.freedesktop.org/show_bug.cgi?id=80419">bug 80419</a>
from <span class="vcard"><a class="email" href="mailto:nhaehnle@gmail.com" title="Nicolai Hähnle <nhaehnle@gmail.com>"> <span class="fn">Nicolai Hähnle</span></a>
</span></b>
<pre>Brief update: The crashes and Valgrind errors when playing back the trace are
almost certainly unrelated to the lockup. It turns out apitrace is too
aggressive in trimming the client-side memory blobs during recording. (See
<a href="https://github.com/apitrace/apitrace/issues/407#issuecomment-167866502">https://github.com/apitrace/apitrace/issues/407#issuecomment-167866502</a>)
On a more positive note, I am also seeing the lockup on Tonga from inside the
game itself. Unfortunately, I cannot reproduce it reliably yet.</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>