https://bugs.kde.org/show_bug.cgi?id=357754
--- Comment #1 from Thomas Lübking <thomas.luebk...@gmail.com> --- Nope, EGL_NO_CONTEXT (ie. 0x0) is deliberate. I assume this crashes in the driver for a simple OOM condition -> driver bug (more or less) @Martin, maybe we should have a sanity check here as well (ie. if it exceeds the max texture size anyway, there's no point in loading it - I assume this happens on glx, preventing the crash with a giant invalid texture)? -- You are receiving this mail because: You are watching all bug changes.
