https://bugs.kde.org/show_bug.cgi?id=357754
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=357754
--- Comment #3 from Fabian Vogt ---
(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
https://bugs.kde.org/show_bug.cgi?id=357754
--- Comment #2 from Martin Gräßlin ---
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 thi
https://bugs.kde.org/show_bug.cgi?id=357754
--- Comment #1 from Thomas Lübking ---
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 exceed
