Created attachment 138954 [details] More infos of KCrash/gdb and glxinfo. This might be a duplicate of #102423 or #103234. (But did not want to pollute these if they were unrelated.) ... #4 0x00007f78f8a4c793 in KCrash::defaultCrashHandler (sig=11) at ./src/kcra... #5 <signal handler called> ... #6 si_emit_draw_packets (sctx=sctx@entry=0x5600dec29f30, info=info@entry=0x... #7 0x00007f78c278d2b0 in si_draw_vbo (ctx=0x5600dec29f30, info=0x5600dec6b1... #8 0x00007f78c24efd03 in tc_call_draw_vbo (pipe=<optimized out>, payload=0x... #9 0x00007f78c24eddff in tc_batch_execute (thread_index=0, job=0x5600dec6a8... ... (gdb) up #6 si_emit_draw_packets (sctx=sctx@entry=0x5600dec29f30, info=info@entry=0x... 713 index_max_size = (indexbuf->width0 - index_offset) / At this point it looks like variable indexbuf is NULL. "bt full" would suggest this too: #7 0x00007f78c278d2b0 in si_draw_vbo (ctx=0x5600dec29f30, info=0x5600dec6b1... ... indexbuf = 0x0 So I cannot reproduce this and was hit just once. But it could be related to the not so long Qt 5.10 update in Debian testing. I took a core dump if there are more questions. All debug symbols are available as far as I see. Related could also be that the core file is of a size of 3.5 GB so that might have led to the NULL pointer. Attached is a file containing the more infos of KCrash/gdb and glxinfo.
A little addition: Looks like I can reliably reproduce by just pressing alt+tab and holding it for some seconds, while on the left the window previews are iterating through. And it looks like the 3.5 core file is not coming from kind of a memory limit, because in htop a such crashed process shows: VIRT: 4452M RES: 216M SHR: 118M And gcore produces a 3.8 GB file of it.
Being able to reproduce it I built a set of mesa packages with the patch from #103234. By adding a fprintf before the return I can confirm that this patch avoids the crash.
*** This bug has been marked as a duplicate of bug 103234 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.