On 2017-12-29 08:36 PM, Felix Kuehling wrote: > Is it possible that the test is broken? A test that allocates memory to > exhaustion may well trigger the OOM killer. A test can do that by using > malloc. Why not by using the graphics driver? The OOM killer does what > it's supposed to do, and kills the broken application. > > As I understand it, this change is adds artificial limitations to > workaround a bug in a user mode test. I'm afraid it's not that simple. While triggering the OOM killer might be acceptable or even expected, hard hangs aren't. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer
