Closed Bug 1576843 Opened 7 years ago Closed 6 years ago

Crash in [@ ssse3::S32_alpha_D32_filter_DX]

Categories

(Core :: Graphics, defect, P3)

68 Branch
defect

Tracking

()

RESOLVED FIXED
83 Branch
Tracking Status
firefox-esr60 --- unaffected
firefox-esr68 --- wontfix
firefox-esr78 82+ fixed
firefox68 --- wontfix
firefox69 --- wontfix
firefox70 --- wontfix
firefox71 --- wontfix
firefox81 --- wontfix
firefox82 --- fixed
firefox83 --- fixed

People

(Reporter: philipp, Unassigned)

References

(Regression)

Details

(4 keywords, Whiteboard: [post-critsmash-triage][adv-main82+r][adv-esr78.4+r])

Crash Data

This bug is for crash report bp-e0efff73-ded8-42b1-a4d5-0449f0190825.

Top 10 frames of crashing thread:

0 xul.dll static void ssse3::S32_alpha_D32_filter_DX gfx/skia/skia/src/opts/SkBitmapProcState_opts.h:141
1 xul.dll void BitmapProcShaderContext::shadeSpan gfx/skia/skia/src/shaders/SkBitmapProcShader.cpp:76
2 xul.dll void SkARGB32_Shader_Blitter::blitH gfx/skia/skia/src/core/SkBlitter_ARGB32.cpp:1005
3 xul.dll SkAAClipBlitter::blitRect gfx/skia/skia/src/core/SkAAClip.cpp:1972
4 xul.dll static void antifilldot8 gfx/skia/skia/src/core/SkScan_Antihair.cpp:683
5 xul.dll SkScan::AntiFillRect gfx/skia/skia/src/core/SkScan_Antihair.cpp
6 xul.dll SkScan::AntiFillRect gfx/skia/skia/src/core/SkScan_Antihair.cpp:813
7 xul.dll SkDraw::drawRect gfx/skia/skia/src/core/SkDraw.cpp:677
8 xul.dll void SkBitmapDevice::drawRect gfx/skia/skia/src/core/SkBitmapDevice.cpp:355
9 xul.dll void SkCanvas::onDrawRect gfx/skia/skia/src/core/SkCanvas.cpp:2088

this cross-platform crash signature is starting to show up in firefox 68, apparently related to bug 1539026.

Flags: needinfo?(lsalzman)

sec-high because it's crashing in an interpolate function, and maybe if it's got the address wrong for one it might next write to a wrong address as well. But otherwise if the worst is a read in graphics this could be lowered to sec-moderate

Keywords: sec-high

Lee - per dveditz's comment - should this be a sec-high?

The problem isn't in Skia here as far as I understand. Rather, something higher up in OMTP is passing in a bad surface, but because this is from an OMTP recording, we don't have any real information on where the surface came from in the crash stack. The crash stacks don't show the memory being obviously wrong either like use-after-free, so this doesn't seem too concerning . We've also always had a low volume of these sorts of crashes occurring down in the Skia surface sampling functions ever since OMTP was introduced, and as yet I don't think we've found anything actionable in the global case to make them go away.

In summary, there could be a multitude of causes here, or at least nothing definitive, and looking at the stacks, not much we can do, and not much to be concerned about right now.

Flags: needinfo?(lsalzman)
Keywords: stalled
Priority: -- → P3
Crash Signature: [@ ssse3::S32_alpha_D32_filter_DX] → [@ ssse3::S32_alpha_D32_filter_DX] [@ hsw::S32_alpha_D32_filter_DX]
Crash Signature: [@ ssse3::S32_alpha_D32_filter_DX] [@ hsw::S32_alpha_D32_filter_DX] → [@ ssse3::S32_alpha_D32_filter_DX] [@ hsw::S32_alpha_D32_filter_DX]

I couldn't figure out what was going on, but it seemed to be caused by minimizing the window with two tabs open:

This should be fixed by 1656987

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
See Also: → 1656987

Since the bug is closed, the stalled keyword is now meaningless.
For more information, please visit auto_nag documentation.

Keywords: stalled
Group: gfx-core-security → core-security-release
Whiteboard: [adv-main82+r]

Clearing advisory flag because the linked bug hasn't landed (completely) yet in beta.

Whiteboard: [adv-main82+r]

Bug 1656987 got uplifted to 82 and 78.4

Target Milestone: --- → 83 Branch
Flags: qe-verify-
Whiteboard: [post-critsmash-triage]
Whiteboard: [post-critsmash-triage] → [post-critsmash-triage][adv-main82+r]
Whiteboard: [post-critsmash-triage][adv-main82+r] → [post-critsmash-triage][adv-main82+r][adv-esr78.4+r]
Group: core-security-release
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.