<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <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#c3">Comment # 3</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 <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to alexander.maznev from <a href="show_bug.cgi?id=90492#c2">comment #2</a>) > Hello Chris, > Thank you for looking at this. I suspect in some-cases it's not running out > of Memory at least directly (when I run with 1GB swap, opening this page > with the firefox fills about 400mgb of the swap [so it's possible to load > 3-4 before experiencing problems], if I turn swapoff, with 3gb RAM free the > system becomes completely unresponsive just after one page load). vmstat > shows a lot of inactive memory which is not being freed when the system runs > low on resources? 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). > Further why isn't oom_killer handling this gracefully? > Firefox has a +100 oomscore over any other running process when this is > triggered and terminating it should return the system to a normal state. You have oom_kill_allocating_task set in sysctl.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>