[Bug 104760] System hang when use glTexImage3D to specify a 3D texture image

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=104760

--- Comment #15 from Kenneth Graunke <kenneth at whitecape.org> ---
I just ran this locally, and indeed got piles of oom-killer.  My system
survived - a couple programs got killed - and Mesa eventually returned
GL_OUT_OF_MEMORY.

I'm not sure what we can do about this, to be honest.  It sounds like the
'system hang' is that the Linux OOM killer torches something critical...which
would be a general Linux problem with being out of memory.

Prior to the bisected patch, Mesa would allocate pages for the texture on the
first access.  Now, it allocates it on creation.  This programs happens to
allocate a texture, and never use it.  But if you ever did use it, you'd suffer
the same fate.  I find it highly unlikely that any real world program would hit
this case - if someone allocates a texture, they probably intend to use it.

Chris, is there some reason that the kernel can't just...swap those pages out? 
Nothing is using them.  Perhaps we should madvise them until first use or
something?  Or, should we avoid allocating huge things (above some threshold)
up front?  Or...really...the OOM killer sabotaging systems seems like a core
Linux problem, and not anything we can do much about...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20180302/cbe6f8c6/attachment-0001.html>