<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Xorg unresponsive under heavy system-load"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90492#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Xorg unresponsive under heavy system-load"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90492">bug 90492</a>
from <span class="vcard"><a class="email" href="mailto:alexander.maznev@gmail.com" title="alexander.maznev@gmail.com">alexander.maznev@gmail.com</a>
</span></b>
<pre>low on resources?
<span class="quote">> Your dmesg indicated the first failure with completely full swap. Though it
> is a known issue that the kernel will start killing processes with swap
> still available. One of the problems here is during the early oom, the GPU
> is still active and itself waiting upon allocations (which is preventing it
> from yielding memory back to the system).</span >
Yes, I turned swap off afterwards to get more consistent behaviour (the thing
with having swap on is if there is some very small amount of space, it will
freeze while aggressively trying to swap stuff around to get memory, so the
system hangs instead of erroring out of xserver).
<span class="quote">> You have oom_kill_allocating_task set in sysctl.</span >
cat /proc/sys/vm/oom_kill_allocating_task
0</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>