Summary: | Crash in eglCreateImageKHR | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Fabian Vogt <fabian> |
Component: | egl | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | 5.5.2 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Fabian Vogt
2016-01-09 18:11:48 UTC
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)? obviously the driver shouldn't crash on a too large pixmap. Given that I'm not sure whether we should check for a work around. After all there might be many more crashy conditions in the driver code. Anyway: I think that should go to upstream bug tracker. Adding a test case for it should be relatively easy - for once in a while we actually know what triggered the crash. (In reply to Martin Gräßlin from comment #2) > Anyway: I think that should go to upstream bug tracker. Adding a test case > for it should be relatively easy - for once in a while we actually know what > triggered the crash. Ok, reported as https://bugs.freedesktop.org/show_bug.cgi?id=93667 Should I leave this report open until it's fixed in Mesa? For the moment, there's little point in this since atm. there's no consideration to workaround this (and it's rather a corner case by accidentally causing OOM conditions in the driver) It's a driver bug per * If insufficient memory is available to complete the specified operation, the error EGL_BAD_ALLOC is generated. Iff the driver devs should be unable to fix it, one might pitch for a workaround again (then just re-open the bug, rant about stubborn driver devs etc. and we'll see what to do about it ;-) |