control: tag -1 moreinfo > #4 0x0000555558e64e4d in base::(anonymous > namespace)::OnNoMemorySize(unsigned long) [clone .constprop.237] () > #5 0x0000555558ef0c85 in calloc () > #6 0x00007fffaa96c7e9 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so > #7 0x00007fffaa45f4b9 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so > #8 0x00007fffaa4cd4b4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so > #9 0x00007fffd87ca1b5 in ?? () from > /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 > #10 0x00007fffd87b6ec9 in ?? () from > /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 > #11 0x00007fffd87b2a64 in ?? () from > /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 > #12 0x00007fffd87b2fde in ?? () from > /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 > #13 0x000055555981d413 in > gl::RealGLXApi::glXQueryExtensionsStringFn(_XDisplay*, int) () [...] > ii libgl1-mesa-dri 19.2.0~rc1-1
I wasn't able to reproduce your problem by upgrading packages to experimental. However, given /usr/lib/x86_64-linux-gnu/dri/i965_dri.so is involved in the backtrace, mesa 19.2.0~rc1 from experimental is most likely the cause. Since I couldn't reproduce it on my system, it is probably specific to your hardware. Could you try updating all of your mesa packages back to experimental and try again? Please also install libgl1-mesa-dri-dbgsym beforehand so we can see what is going on in the ?? parts of the backtrace. Best wishes, Mike
