Open Bug 1971223 Opened 1 year ago Updated 4 days ago

Crash in [@ fill_n<T>]

Categories

(Core :: Graphics: WebRender, defect)

ARM64
All
defect

Tracking

()

Tracking Status
firefox141 --- affected

People

(Reporter: release-mgmt-account-bot, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/3ba21c54-387d-46fb-875b-6c1a90250521

Reason: EXC_BAD_ACCESS / KERN_PROTECTION_FAILURE

Top 10 frames of crashing thread:

0  XUL  fill_n<unsigned int>  gfx/wr/swgl/src/gl.cc:2118
0  XUL  commit_solid_span<false>  gfx/wr/swgl/src/blend.h:840
0  XUL  ps_quad_textured_frag::swgl_drawSpanRGBA8  aarch64-apple-darwin/release/build/swgl-afd9d81ae467228a/out/ps_quad_textured.h:733
0  XUL  ps_quad_textured_frag::draw_span_RGBA8  aarch64-apple-darwin/release/build/swgl-afd9d81ae467228a/out/ps_quad_textured.h:782
1  XUL  glsl::FragmentShaderImpl::draw_span  gfx/wr/swgl/src/program.h:168
1  XUL  draw_depth_span<unsigned int>  gfx/wr/swgl/src/rasterize.h:628
1  XUL  draw_quad_spans<unsigned int>  gfx/wr/swgl/src/rasterize.h:1025
2  XUL  draw_quad  gfx/wr/swgl/src/rasterize.h:1625
3  XUL  draw_elements<unsigned short>  gfx/wr/swgl/src/rasterize.h:1658
3  XUL  DrawElementsInstanced  gfx/wr/swgl/src/gl.cc:2748

By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:

  • First crash report: 2025-04-28
  • Process type: Parent
  • Is startup crash: No
  • Has user comments: No
  • Is null crash: No
Component: General → Graphics: WebRender

The severity field is not set for this bug.
:gw, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(gwatson)

Any ideas Lee? Probably nothing actionable from this?

Severity: -- → S3
Flags: needinfo?(gwatson) → needinfo?(lsalzman)

This is extremely low volume and I don't know that there is any pattern observable yet that could clue us in what is causing it.

Flags: needinfo?(lsalzman)
Severity: S3 → S4
You need to log in before you can comment on or make changes to this bug.