<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#c1">Comment # 1</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>You ran out of memory (including swap). The kernel cannot execute the GPU commands due to memory exhaustion and that eventually lands in an untrapped SIGBUS. The segfault is a bug elsewhere in the xserver. It is unresponsive due to the amount of swap thrashing... For example, the first Xorg.0.log, the crash is due to not being able to page in a library from disk. The second didn't have enough memory even to do symbol lookups in the backtrace. The third is a segfault during client shutdown, but it is not clear where. The last one is the only one that looks like the ddx should have prevented but didn't (the ddx is aware that accessing a mmap() may cause a SIGBUS due to oom and tries to trap them) -- however, symbol lookup failed. So for what it is worth, I added a few missing traps around pixman_fill based on the Xorg.0.log you reported on irc: commit 335ac8742e9eadcdf8f087b24f84c7df0fda31c0 Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Date: Sun May 17 08:53:45 2015 +0100 sna: Wrap CPU access for composite operations with sigtrap</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>