Bug#832452: twinkle: Crashes during call when switching desktop

[thomas schorpp <thomas.schorpp@gmail.com>]

Am 30.07.2016 um 19:06 schrieb Lisandro Damián Nicanor Pérez Meyer:

> Hi Peter! Looking at the not complete backtraces (the i965_dri one misses the
> i965_dri 's debugging symbols and there is not a complete nouveau backtrace)
> it really seems a bug on those two drivers, not in Qt itself.

OK, Installed libgl1-mesa-dri-dbg:amd64 (10.3.2-1+deb8u1)

twinkle:
(gdb) bt full
#0  brw_workaround_depthstencil_alignment (brw=0x55555640ec98, clear_mask=clear_mask@entry=50)
    at ../../../../../../../src/mesa/drivers/dri/i965/brw_misc_state.c:241
        fb = 0x0
        stencil_draw_x = 0
        stencil_draw_y = 0
        tile_mask_x = 4
        tile_mask_y = 0
#1  0x00007fffdb573962 in brw_clear (ctx=0x55555640ec98, mask=50) at ../../../../../../../src/mesa/drivers/dri/i965/brw_clear.c:235
        fb = 0x5555573646a0
        partial_clear = false
        tri_mask = <optimized out>
#2  0x00007ffff504aafc in QSGBatchRenderer::Renderer::renderBatches() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
No symbol table info available.
...

totem:
(gdb) bt full
#0  brw_workaround_depthstencil_alignment (brw=0x555555ad1388, clear_mask=clear_mask@entry=0)
    at ../../../../../../../src/mesa/drivers/dri/i965/brw_misc_state.c:241
        fb = 0x0
        stencil_draw_x = 0
        stencil_draw_y = 0
        tile_mask_x = 1453310160
        tile_mask_y = 21845
#1  0x00007fffdeaba962 in brw_clear (ctx=0x555555ad1388, mask=18) at ../../../../../../../src/mesa/drivers/dri/i965/brw_clear.c:235
        fb = 0x55555709e800
        partial_clear = true
        tri_mask = <optimized out>
#2  0x00007ffff5f12312 in cogl_framebuffer_clear4f () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
No symbol table info available.
#3  0x00007ffff6626827 in ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
No symbol table info available.
#4  0x00007ffff68d788a in ?? () from /usr/lib/x86_64-linux-gnu/libclutter-gtk-1.0.so.0
No symbol table info available.
#5  0x00007ffff1cd0e8f in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
No symbol table info available.
...

Remember, this may not reflect the real issue at first occurance due to possibly wrecked HW state caused from the 1st occurance,
I'm going to try reproducing the 1st occurance state after next cold boot.

y
tom