<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED --- - xserver freezes"
href="https://bugs.freedesktop.org/show_bug.cgi?id=76892#c23">Comment # 23</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED --- - xserver freezes"
href="https://bugs.freedesktop.org/show_bug.cgi?id=76892">bug 76892</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>Odd. What I would say that is the blockhandler, which implies that some client
is sending lots of non-rendering requests. It doesn't suggest that the
DDX/Xserver is trapped in a loop though, just doing busy-work.
You may find that "sudo perf top" gives a clue, but really you want a log of
the requests made by each client. I guess one thing to check is whether this is
a recent regression in the ddx (i.e. try 2.99.910 etc). The other approach as
you have a highly reproducible scenario is that grabbing a full-debug log is
promising (compile the ddx with ./configure --enable-debug=full)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>