control: tag -1 moreinfo On Sat, Oct 26, 2019 at 10:48 AM Witold Baryluk wrote: > Thread 20 "Chrome_InProcGp" received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x7fffaa7fc700 (LWP 32634)] > 0x00007fff770d9c37 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so > (gdb) bt > #0 0x00007fff770d9c37 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so > #1 0x00007fff76f76409 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so > #2 0x0000555559e1d3b1 in > gpu::gles2::GLES2DecoderImpl::InvalidateFramebufferImpl(unsigned int, int, > unsigned int const volatile*, int, int, int, int, char const*, > gpu::gles2::GLES2DecoderImpl::FramebufferOperation) () > #3 0x0000555559e2030a in > gpu::gles2::GLES2DecoderImpl::HandleInvalidateFramebufferImmediate(unsigned > int, void const volatile*) () > #4 0x0000555559dfa261 in gpu::error::Error > gpu::gles2::GLES2DecoderImpl::DoCommandsImpl<false>(unsigned int, void const > volatile*, int, int*) ()
This looks like an error in the RadeonSI driver. Could you try installing libgl1-mesa-dri-dbgsym to fill in the ?? in the backtrace? Best wishes, Mike
