Closed Bug 1457167 Opened 7 years ago Closed 6 years ago

Crash in S32_opaque_D32_filter_DX_SSSE3

Categories

(Core :: Graphics, defect, P3)

x86
Android
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox-esr52 --- unaffected
firefox-esr60 --- unaffected
firefox59 --- wontfix
firefox60 --- wontfix
firefox61 --- wontfix
firefox62 --- wontfix

People

(Reporter: marcia, Unassigned)

Details

(Keywords: crash, regression, Whiteboard: [gfx-noted])

Crash Data

This bug was filed from the Socorro interface and is report bp-e4959aa6-79ca-45db-8b90-b09140180426. ============================================================= Seen while looking at beta crash stats - this fairly small volume crash so far affects betas starting at b12: https://bit.ly/2FiZYf6 Perhaps a Skia update in 60 might be responsible? Seems to primarily affect a set of Samsung devices running API22. Top 6 frames of crashing thread: 0 libxul.so S32_opaque_D32_filter_DX_SSSE3 gfx/skia/skia/src/opts/SkBitmapProcState_opts_SSSE3.cpp:161 1 dalvik-main space (deleted) dalvik-main space @0x2efbffff 2 dalvik-main space (deleted) dalvik-main space @0x2fe4ffff 3 libxul.so BitmapProcShaderContext::shadeSpan gfx/skia/skia/src/shaders/SkBitmapProcShader.cpp:77 4 libxul.so libxul.so@0x20a52ef 5 libxul.so libxul.so@0x20a444f =============================================================
I'm going to assume we'll see this on 61 as well once it reaches Beta in a bit over a week.
Crash log seems wired. Crash stack and crash log says that architecture is x86, but Adapter Vendor ID was Qualcomm and it has Adreno 540/530/510. Then architecture should be arm.
:snorp, do you know why the crash info says that "Qualcomm + Adreno" and x86?
Flags: needinfo?(snorp)
It looks to me like someone is trying to fake a Samsung device on an x86 emulator or similar. I wouldn't worry about this one too much.
Flags: needinfo?(snorp)
Whiteboard: [gfx-noted]

No crashes in recent builds. Resolving as WFM.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.