Open Bug 1917248 Opened 2 years ago Updated 8 months ago

Thunderbird (mostly) startup crash in [@ mozilla::gfx::ToDeviceColor] (buggy intel raptor lake cpu)

Categories

(Thunderbird :: General, defect, P3)

Thunderbird 128
Unspecified
Windows 10
defect

Tracking

(thunderbird_esr128 affected, thunderbird_esr140 affected, thunderbird141 affected)

Tracking Status
thunderbird_esr128 --- affected
thunderbird_esr140 --- affected
thunderbird141 --- affected

People

(Reporter: wsmwk, Unassigned)

References

(Blocks 2 open bugs)

Details

(Keywords: crash, Whiteboard: [tbird crash])

Crash Data

Crashes are mostly Thunderbird, and all version 128 and recent betas.

Crash report: https://crash-stats.mozilla.org/report/index/6f5d0548-33e1-40a4-847c-044360240906

Reason: EXCEPTION_STACK_BUFFER_OVERRUN / FAST_FAIL_STACK_COOKIE_CHECK_FAILURE

Top 10 frames:

0  xul.dll  __report_gsfailure(unsigned long long)  /builds/worker/workspace/obj-build/toolkit/library/build/D:/a/_work/1/s/src/vctools/crt/vcstartup/src/gs/gs_report.c:220
1  xul.dll  mozilla::gfx::ToDeviceColor(unsigned int)  gfx/thebes/gfxUtils.cpp:1800
2  xul.dll  mozilla::SVGEmbeddingContextPaint::SetStroke(unsigned int)  layout/svg/SVGContextPaint.h:252
2  xul.dll  mozilla::SVGImageContext::MaybeStoreContextPaint(mozilla::SVGImageContext&, n...  layout/svg/SVGImageContext.cpp:66
3  xul.dll  nsLayoutUtils::ComputeImageContainerDrawingParameters(imgIContainer*, nsIFram...  layout/base/nsLayoutUtils.cpp:6500
4  xul.dll  mozilla::nsImageRenderer::BuildWebRenderDisplayItems(nsPresContext*, mozilla:...  layout/painting/nsImageRenderer.cpp:617
5  xul.dll  mozilla::nsImageRenderer::BuildWebRenderDisplayItemsForLayer(nsPresContext*, ...  layout/painting/nsImageRenderer.cpp:775
5  xul.dll  nsCSSRendering::BuildWebRenderDisplayItemsForStyleImageLayerWithSC(nsCSSRende...  layout/painting/nsCSSRendering.cpp:2728
6  xul.dll  nsCSSRendering::BuildWebRenderDisplayItemsForStyleImageLayer(nsCSSRendering::...  layout/painting/nsCSSRendering.cpp:1957
6  xul.dll  mozilla::nsDisplayBackgroundImage::CreateWebRenderCommands(mozilla::wr::Displ...  layout/painting/nsDisplayList.cpp:3409
Version: unspecified → Thunderbird 128
Component: General → Layout
Product: Thunderbird → Core
Version: Thunderbird 128 → unspecified

-> Graphics, but it seems it might be a separate bug in thunderbird corrupting the stack or something? Because I don't see how that code would cause a stack buffer overrun.

Component: Layout → Graphics

All of these crashes are on family 6 model 183 stepping 1 which is the known buggy intel raptor lake cpu.

Blocks: cpu-bugs
Severity: -- → S3
Priority: -- → P3

Moving back to Thunderbird

Component: Graphics → General
Product: Core → Thunderbird
Summary: Crash in [@ mozilla::gfx::ToDeviceColor] → Crash in [@ mozilla::gfx::ToDeviceColor] (buggy intel raptor lake cpu?)
Whiteboard: [tbird crash]
Version: unspecified → Thunderbird 128
Summary: Crash in [@ mozilla::gfx::ToDeviceColor] (buggy intel raptor lake cpu?) → Crash in [@ mozilla::gfx::ToDeviceColor] (buggy intel raptor lake cpu)

User at https://www.reddit.com/r/Thunderbird/comments/1oxo0s5/comment/npbu8g0/ indicates https://crash-stats.mozilla.org/report/index/a394c44e-a4ee-4085-af26-882720251117 (5 second uptime) is happening even with bios updated. The crash doesn't indicate bios version, so I will ask the user.

Summary: Crash in [@ mozilla::gfx::ToDeviceColor] (buggy intel raptor lake cpu) → Thunderbird (mostly) Crash in [@ mozilla::gfx::ToDeviceColor] (buggy intel raptor lake cpu)

Crash rate is down ~30% compared to a month ago, so about same as late spring 6 months ago.

Summary: Thunderbird (mostly) Crash in [@ mozilla::gfx::ToDeviceColor] (buggy intel raptor lake cpu) → Thunderbird (mostly) startup crash in [@ mozilla::gfx::ToDeviceColor] (buggy intel raptor lake cpu)

(In reply to Wayne Mery (:wsmwk) from comment #5)

User at https://www.reddit.com/r/Thunderbird/comments/1oxo0s5/comment/npbu8g0/ indicates https://crash-stats.mozilla.org/report/index/a394c44e-a4ee-4085-af26-882720251117 (5 second uptime) is happening even with bios updated. The crash doesn't indicate bios version, so I will ask the user.

User updated bios to 2025-09-10

See Also: → 1981802
You need to log in before you can comment on or make changes to this bug.