Created attachment 372228 [details] Backtrace I can reproduce this reliably while browing my Twitter timeline. Unfortunately I cannot seem to isolate the exact tweet that is causing this. Thread 1 "WebKitWebProces" received signal SIGSEGV, Segmentation fault. scaled_bilinear_scanline_sse2_8888_8888_OVER (zero_src=0, max_vx=2147483647, unit_x_=62415, vx_=<optimized out>, wb=<optimized out>, wt=<optimized out>, w=440, src_bottom=0x7f6c1f300000, src_top=0x7f6c1f2ff880, mask=<synthetic pointer>, dst=0x7f6c14584000) at ../../pixman/pixman-sse2.c:5851 5851 BILINEAR_INTERPOLATE_FOUR_PIXELS (xmm_src); (gdb) print xmm_src $1 = <optimized out>
Can you still reproduce this?
I haven't seen it in a while with 2.24.3, I guess you can close this and I'll reopen if it happens again.
FTR, I've been able to trigger this fairly often scrolling / resizing the browser in Twitter as well. It's really hard to trigger reliably.
Ok, reopening then
I was getting a reliable reproducer today on Twitter. What seems to have fixed it here is upgrading pixman 0.34->0.38. I also upgrading cairo 1.15.10->1.17.2 and the crashes seem to have stopped. I don't have time to bisect and find the minimal supported configuration now, but it seems users need newer versions of these packages than was is currently available in Debian/Ubuntu.
This is very old, I'm closing it.