Created attachment 81320 [details]
kwin gdb

It's an OOM bug, that doesn't mean the source is necessarily equal to that of bug #315089 (selecting an MSAA drawable)

Do you a GL screensaver/locker?

Please attach at least /var/log/Xorg.0.log and the output of "qdbus org.kde.kwin /KWin supportInformation"

Created attachment 81321 [details]
qdbus org.kde.kwin /KWin supportInformation

Created attachment 81322 [details]
/var/log/Xorg.0.log.old (created during crash)

> Do you a GL screensaver/locker?
I do not have screensavers installed, how can i know if my locker is GL? I use default locker from kde.

(In reply to comment #5)
> > Do you a GL screensaver/locker?
> I do not have screensavers installed, how can i know if my locker is GL?
No fancy animation -> no GL screensaver.

Is it the screenlocker with plasmoids on it or just the login dialog?
You could try in "kcmshell4 kwincompositing", 3rd tab, DISable "Suspend compositing for fullscreen windows" (but that's just a wild guess)

Another wild guess:
if it's not a notebook, try unplugging mouse/keyboard after locking (warning, it could happen that the X11 server can not re-enable them afterwards, so don't risk data loss)

@Martin:
The Xorg log has

------------
(EE) [mi] EQ overflowing.  Additional events will be discarded until existing events are processed.
(EE) 
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x47) [0x1540dce907]
(EE) 1: /usr/bin/X (mieqEnqueue+0x2a3) [0x1540dad093]
(EE) 2: /usr/bin/X (0x1540bee000+0x7172d) [0x1540c5f72d]
(EE) 3: /usr/lib64/xorg/modules/input/evdev_drv.so (0x3b1f6441000+0x6818) [0x3b1f6447818]
(EE) 4: /usr/bin/X (0x1540bee000+0xa2bc7) [0x1540c90bc7]
(EE) 5: /usr/bin/X (0x1540bee000+0xd3ea8) [0x1540cc1ea8]
(EE) 6: /lib64/libpthread.so.0 (0x3b1faf2b000+0xf2c0) [0x3b1faf3a2c0]
(EE) 7: /lib64/libc.so.6 (ioctl+0x7) [0x3b1f9c82ac7]
(EE) 8: /usr/lib64/libdrm.so.2 (drmIoctl+0x38) [0x3b1fad20a58]
(EE) 9: /usr/lib64/libdrm_radeon.so.1 (0x3b1f85bd000+0x2503) [0x3b1f85bf503]
(EE) 10: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x3b1f87cb000+0x1e8fa) [0x3b1f87e98fa]
(EE) 11: /usr/lib64/xorg/modules/libexa.so (0x3b1f7f8e000+0x90f7) [0x3b1f7f970f7]
(EE) 12: /usr/bin/X (0x1540bee000+0x15bae2) [0x1540d49ae2]
(EE) 13: /usr/bin/X (0x1540bee000+0x114f6a) [0x1540d02f6a]
(EE) 14: /usr/bin/X (FreePicture+0x18c) [0x1540d39d7c]
(EE) 15: /usr/bin/X (0x1540bee000+0x81842) [0x1540c6f842]
(EE) 16: /usr/bin/X (FreeClientResources+0x8a) [0x1540c70cda]
(EE) 17: /usr/bin/X (CloseDownClient+0x6a) [0x1540c474fa]
(EE) 18: /usr/bin/X (0x1540bee000+0x5a156) [0x1540c48156]
(EE) 19: /usr/bin/X (0x1540bee000+0x46a94) [0x1540c34a94]
(EE) 20: /lib64/libc.so.6 (__libc_start_main+0xed) [0x3b1f9bc637d]
(EE) 21: /usr/bin/X (0x1540bee000+0x46df1) [0x1540c34df1]
--------------

You mentioned similar (causing a hung GPU) but in relation with synaptics, which is not available here.
Did it look similar and was that on your radeon chip and/or in relation to screenlocking as well?

> Is it the screenlocker with plasmoids on it or just the login dialog?

No plasmoids, just wallpaper + unlock/switch user dialog.

Not laptop, desktop.

On Wednesday 24 July 2013 19:20:03 you wrote:
> You mentioned similar (causing a hung GPU) but in relation with synaptics,
> which is not available here.
> Did it look similar and was that on your radeon chip and/or in relation to
> screenlocking as well?
Kind of similar as far as one can say with lacking debug symbols, but it was 
on SandyBridge and not related to screen locking. Also the problem hasn't 
occurred for quite some time - I assume that one of the recent package 
upgrades fixed it

Crashed again today, do you need gdb output?

Is it any different from the present one?

Did you try in "kcmshell4 kwincompositing", 3rd tab, to DISable "Suspend compositing for fullscreen windows"?

> Is it any different from the present one?
Not much, almost same.

> Did you try in "kcmshell4 kwincompositing", 3rd tab, to DISable "Suspend compositing for fullscreen windows"?

Not yet, and i need this feature.

(In reply to comment #11)

> Not yet, and i need this feature.
Why?
(There's been repetitive discussion to remove it and we just blocked it for intel systems, because the driver(s) happily crash(es) for it)

This time i was testing disabling compositing: kwin did not crash, but there was a black screen some time.
Before next screen lock i will keep compositing enabled, but will disable "Suspend compositing for fullscreen windows".

Isn't this feature useful for 3d games and opengl based video outputs in mpv and vlc?

> but there was a black screen some time.
You mean like the screen remained black for a longer time ad things went on after normally?
Was there a mouse cursor and did it move?

> sn't this feature useful for 3d games and opengl based video outputs in mpv and vlc?
http://kde-look.org/content/show.php/GameMode?content=156659
Esp. for 3d games it frees more resources.

> Isn't this feature useful for 3d games and opengl based video outputs in mpv
> and vlc?
No :-) I'm currently doing real world testing with playing Left for Dead 2 on 
a crappy SandyBridge with compositing enabled and I cannot notice any frame 
drops. The importance is that the game renders well, not that we get high 
number of frames - the screen caps at 60 fps anyway. Just Phoronix tests will 
tell you that we cannot do 254 fps. Differences in the area: the kernel 
sneezes.

not much we can still do here - it's on OOM situation.