Closed Bug 1789922 Opened 3 years ago Closed 3 years ago

Crash in [@ linear_blit<T>]

Categories

(Core :: Graphics: WebRender, defect)

defect

Tracking

()

RESOLVED FIXED
106 Branch
Tracking Status
firefox-esr91 --- unaffected
firefox-esr102 --- unaffected
firefox104 --- unaffected
firefox105 --- unaffected
firefox106 --- fixed

People

(Reporter: mccr8, Assigned: sotaro)

References

Details

(Keywords: crash, regression)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/79731cec-a880-41ef-9b59-2e5b00220908

Reason: SIGSEGV / SEGV_ACCERR

Top 9 frames of crashing thread:

0 libxul.so linear_blit<true> gfx/wr/swgl/src/composite.h:408
1 libxul.so Composite gfx/wr/swgl/src/composite.h:584
2 libxul.so webrender::compositor::sw_compositor::SwCompositeThread::process_job gfx/wr/webrender/src/compositor/sw_compositor.rs:517
3 libxul.so std::sys_common::backtrace::__rust_begin_short_backtrace library/std/src/sys_common/backtrace.rs:122
4 libxul.so core::ops::function::FnOnce::call_once{{vtable.shim}} library/core/src/ops/function.rs:248
5 libxul.so std::sys::unix::thread::Thread::new::thread_start library/std/src/sys/unix/thread.rs:108
6 firefox-bin set_alt_signal_stack_and_start toolkit/crashreporter/pthread_create_interposer/pthread_create_interposer.cpp:80
7 libc.so.6 start_thread /usr/src/debug/glibc-2.35-15.fc36.x86_64/nptl/pthread_create.c:442
8 libc.so.6 __clone3 

(In reply to Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout) from comment #1)

Could this be from bug 1781740?

Yes, it could be from bug 1781740. The regression seemed to be addressed by Bug 1789658.

Flags: needinfo?(sotaro.ikeda.g)
Severity: S2 → S3

No crashes since bug 1789658 landed.

Assignee: nobody → sotaro.ikeda.g
Status: NEW → RESOLVED
Closed: 3 years ago
Depends on: 1789658
Resolution: --- → FIXED
Target Milestone: --- → 106 Branch

Copying crash signatures from duplicate bugs.

Crash Signature: [@ linear_blit<T>] → [@ linear_blit<T>] [@ webrender::device::gl::TextureUploader::upload]
You need to log in before you can comment on or make changes to this bug.