Closed Bug 1622592 Opened 5 years ago Closed 4 years ago

sw-wr: Crash in [@ draw_quad_spans<T>]

Categories

(Core :: Graphics: WebRender, defect, P3)

x86_64
Linux
defect

Tracking

()

RESOLVED FIXED
Tracking Status
firefox-esr68 --- unaffected
firefox73 --- unaffected
firefox74 --- unaffected
firefox75 --- unaffected
firefox76 --- disabled

People

(Reporter: jan, Assigned: lsalzman)

References

(Blocks 1 open bug)

Details

(Keywords: crash, nightly-community)

Crash Data

Attachments

(1 file)

Nightly 20200314214233, KDE, X11, Debian Testing, Macbook Pro
No STR yet. (This is my main profile and I also had gfx.webrender.program-binary-disk;true.)

This bug is for crash report bp-b054d57f-b6fb-4eec-899d-3dfcb0200315.

Top 10 frames of crashing thread:

0 libxul.so void draw_quad_spans<unsigned int> gfx/wr/swgl/src/vector_type.h:413
1 libxul.so draw_quad gfx/wr/swgl/src/gl.cc:2863
2 libxul.so DrawElementsInstanced gfx/wr/swgl/src/gl.cc:2958
3 libxul.so <gleam::gl::ErrorReactingGl<F> as gleam::gl::Gl>::draw_elements_instanced third_party/rust/gleam/src/gl.rs:94
4 libxul.so webrender::renderer::Renderer::draw_instanced_batch gfx/wr/webrender/src/renderer.rs:3778
5 libxul.so webrender::renderer::Renderer::draw_alpha_batch_container gfx/wr/webrender/src/renderer.rs:4109
6 libxul.so webrender::renderer::Renderer::draw_frame gfx/wr/webrender/src/renderer.rs:4046
7 libxul.so webrender::renderer::Renderer::render_impl gfx/wr/webrender/src/renderer.rs:3287
8 libxul.so webrender::renderer::Renderer::render gfx/wr/webrender/src/renderer.rs:3041
9 libxul.so wr_renderer_render gfx/webrender_bindings/src/bindings.rs:584

Priority: -- → P3
Assignee: nobody → lsalzman
Status: NEW → ASSIGNED
Keywords: leave-open
Pushed by lsalzman@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b9fb85847a3f add some padding to SWGL composition buffer to account for SIMD masking. r=jrmuizel

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Assignee: lsalzman → nobody
Severity: normal → S3
Status: ASSIGNED → NEW
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Assignee: nobody → lsalzman
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: