Comment 16 for bug 706117

Fwiw, it's not absolutely certain X is the root cause - the crashes that the backtraces illustrate are due to programming errors in the error handling code.

Basically something goes wrong in the system, yada yada, we run out of memory, then X is unable to do stuff because it's out of memory and starts receiving null pointers for memory allocation, and some of the X code doesn't check the return values of the memory allocation calls and so crashes.

So, the X crashes are a symptom rather than a root cause here. The real question is why is it running out of memory? Is it X? The kernel? Is it something in the test harness itself? Hard to guess based on the info at hand, but I think figuring that out is the next step.